An automated configuration method and apparatus

Abstract

The application provides an automatic configuration method and device, and relates to the technical field of communication. In the method, an automatic configuration instruction of a target network device is received, and the automatic configuration instruction carries a first timestamp of the target network device; when the target network device meets a configuration condition, a second timestamp of the target network device recorded locally is acquired; if the first timestamp is the same as the second timestamp, and a sub-network topology corresponding to the target network device is stable, the target network device is automatically configured, and the sub-network topology is a network topology formed by topology links to which topology nodes corresponding to the target network device belong in a global network topology currently recorded by the SDN controller. The method realizes automatic configuration of network devices corresponding to a local network topology in a stable state in a network topology when the network topology changes, so as to better cope with changes in the network topology.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to an automated configuration method and apparatus. Background Technology

[0002] Software-Defined Networking (SDN) automation refers to the automated process of network management and configuration using SDN technology. SDN is a network architecture that separates network control from data forwarding, managing and configuring network devices through a centralized controller. In SDN technology, automated configuration is typically achieved using network topology, generally including the following basic processes: determining the network topology, configuring the SDN controller, writing automation scripts, and deploying the automation scripts.

[0003] To achieve centralized management and control of all network devices, all network devices can be centralized in a Fabric (interwoven network), and automated configuration can be completed using the aforementioned automated configuration process. While this automated configuration process helps administrators manage and configure network devices more efficiently in complex network environments, implementing SDN automation based on network topology requires a stable network topology before implementation. Because topology instability can lead to changes in the connections, locations, or configurations of network devices, if the SDN automation scripts still use the previous network topology information when configuring network devices, configuration errors may occur due to applying configurations to incorrect network devices or ports.

[0004] For example, as business expands, the number of network devices increases, and the network topology expands accordingly. Inevitably, some network devices or device ports will fail, causing the entire network topology to constantly change. However, within this network topology, there are generally localized stable topologies; that is, a change in the topology of a particular link does not affect the state of other localized topologies. Based on this scenario, according to current automated configuration methods, the SDN controller needs global topology stability before it can automatically configure network devices across the entire network topology. This results in low flexibility in automated configuration and an inability to effectively handle changes in network topology. Summary of the Invention

[0005] In view of this, this application provides an automated configuration method and apparatus to flexibly respond to changes in network topology and improve the flexibility of automated configuration.

[0006] Specifically, this application is implemented through the following technical solution:

[0007] According to a first aspect of this application, an automated configuration method is provided, applied in an SDN controller, the method comprising:

[0008] Receive an automated configuration instruction for the target network device, wherein the automated configuration instruction carries the first timestamp of the target network device;

[0009] When the target network device meets the configuration conditions, obtain the second timestamp of the target network device recorded locally;

[0010] If the first timestamp is the same as the second timestamp, and the sub-network topology corresponding to the target network device is stable, then the target network device is automatically configured. The sub-network topology is the network topology consisting of the topology links to which the topology node corresponding to the target network device belongs, which is included in the global network topology currently recorded by the SDN controller.

[0011] According to a second aspect of this application, an automated configuration device is provided, disposed in an SDN controller, the device comprising:

[0012] A receiving module is used to receive an automated configuration instruction from a target network device, wherein the automated configuration instruction carries a first timestamp of the target network device.

[0013] The acquisition module is used to acquire the second timestamp of the target network device recorded locally when the target network device meets the configuration conditions;

[0014] The configuration module is used to automatically configure the target network device if the first timestamp is the same as the second timestamp and the sub-network topology corresponding to the target network device is stable. The sub-network topology is the network topology consisting of the topology links to which the topology node corresponding to the target network device belongs, which is included in the global network topology currently recorded by the SDN controller.

[0015] According to a third aspect of this application, an electronic device is provided, including a processor and a machine-readable storage medium storing a computer program executable by the processor, the processor being prompted by the computer program to perform the method provided in the first aspect of the embodiments of this application.

[0016] According to a fourth aspect of this application, a machine-readable storage medium is provided, which stores a computer program that, when invoked and executed by a processor, causes the processor to perform the method provided in the first aspect of the embodiments of this application.

[0017] The beneficial effects of the embodiments of this application are as follows:

[0018] In the automated configuration method and apparatus provided in this application embodiment, an automated configuration instruction for a target network device is received, the automated configuration instruction carrying a first timestamp of the target network device; when the target network device meets the configuration conditions, a second timestamp of the target network device recorded locally is obtained; if the first timestamp is the same as the second timestamp, and the sub-network topology corresponding to the target network device is stable, then the target network device is automatically configured.

[0019] In the aforementioned process, since the sub-network topology is the network topology consisting of the topology links of the topology node corresponding to the target network device included in the global network topology currently recorded by the SDN controller, even if the global network topology is unstable, by providing the aforementioned automated configuration method, when the target network device is configurable, and the first timestamp is the same as the second timestamp, and the sub-network topology corresponding to the target network device is stable, the target network device can be automatically configured. This achieves the goal of automatically configuring network devices corresponding to local network topologies that are in a stable state in the network topology even when the network topology changes, so as to better cope with changes in the network topology and improve the flexibility of automated configuration. Attached Figure Description

[0020] Figure 1a This application provides a schematic diagram of the network structure to which the initial network topology belongs;

[0021] Figure 1b This is a network topology diagram provided in this application;

[0022] Figure 2 This is a flowchart illustrating an automated configuration method provided in an embodiment of this application;

[0023] Figure 3 This is a schematic diagram of the structure of an automated configuration device provided in an embodiment of this application;

[0024] Figure 4 This is a schematic diagram of the hardware structure of an electronic device implementing an automated configuration method, provided in an embodiment of this application. Detailed Implementation

[0025] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application.

[0026] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used herein are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the corresponding listed items.

[0027] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0028] In practical applications, the Link Layer Discovery Protocol (LLDP) can help network devices automatically discover and obtain information such as the identifiers, capabilities, and network configurations of neighboring devices. This enables operations such as topology discovery, neighbor relationship management, and configuration optimization. Current SDN controllers construct the initial, unconfigured network topology by listening to LLDP messages actively pushed by network devices. Figure 1a As shown, the specific process is as follows: (1) The user registers the device serial number of the network device in the SDN controller and powers on the network device; (2) The DHCP (Dynamic Host Configuration Protocol) server automatically assigns a VLAN1 address to the network device and informs the network device of the address of the SDN controller through a DHCP message; (3) After receiving the above DHCP message, the network device uses the address of the SDN controller carried in the message to try to establish a communication channel with the SDN controller; (4) When the SDN controller receives the communication channel establishment request, it will verify the device serial number of the requesting network device. Since the SDN controller only allows communication channels to be established with registered network devices, after the channel is established, the SDN controller subscribes to the network device for LLDP message push; (5) The SDN controller constructs the initial network topology based on the connection status of the communication channel and the basic device information, LLDP information and other data of the network device that can be queried through the communication channel.

[0029] The inventors discovered that as business expands, network devices may change. To update the network topology, the SDN controller can receive interactive events from network devices under the Fabric that affect topology data. These events carry information such as device online / offline status and LLDP changes. Based on this, the SDN controller can update the timestamp information of the Fabric global topology. The automated configuration process is roughly as follows: When a user accesses the network topology page through a client, the SDN controller returns the timestamp information of the stable global network topology in the Fabric to the client and records it. When the user selects a topology node for automated deployment, the client sends back the previously recorded global topology timestamp information to the SDN controller. The SDN controller compares the timestamp of the global topology returned by the client with the latest timestamp recorded by the SDN controller to prevent the automated task from starting if there are topology changes across the network. After the automated task is completed, the SDN controller generates automated data for the network devices and their links to mark the network devices and links as having completed automation.

[0030] The inventors also discovered that the aforementioned automated configuration process can only be executed when the global timestamp information returned by the client matches the latest global topology timestamp information recorded in the SDN controller; that is, when the network topology of the entire network has not changed and is in a stable state. However, changes in network devices within Fabric are uncontrollable, and combined with... Figure 1b The network topology shown is explained below. As services expand, Figure 1b The network shown has added a network device C, which needs to be automatically configured. However, if one of the uplink ports of network device A fails, network device A will continuously report LLDP messages to the SDN controller. According to the current automatic configuration scheme, the SDN controller will continuously prompt the user that the current network topology under Fabric is unstable and needs to refresh the global topology. Only after the global topology is stable can the network device C under Fabric be automatically configured.

[0031] However, from the user's perspective, Figure 1b If network devices D and E are fault-free, and the links between these two network devices and network device C are stable, then the SDN controller should allow device C to perform automated configuration. Therefore, the inventors found that existing automated configuration schemes suffer from low configuration flexibility and cannot achieve automated configuration of network devices corresponding to locally stable network topologies, thus failing to adequately address changes in network topologies.

[0032] In view of this, this application proposes an automated configuration method applied to an SDN controller. The method's process is as follows: receiving an automated configuration instruction for a target network device, the instruction carrying a first timestamp of the target network device; when the target network device meets the configuration conditions, obtaining a second timestamp of the target network device recorded locally; if the first timestamp and the second timestamp are the same, and the sub-network topology corresponding to the target network device is stable, then automatically configuring the target network device. Since the aforementioned sub-network topology is a network topology consisting of the topology links of the topology node corresponding to the target network device included in the global network topology currently recorded by the SDN controller, even if the global network topology is unstable, by providing the aforementioned automated configuration method, when the target network device is configurable, and the first timestamp and the second timestamp are the same, and the sub-network topology corresponding to the target network device is stable, the target network device can be automatically configured. This achieves the goal of automatically configuring network devices corresponding to stable local network topologies even when the network topology changes, thus better addressing changes in network topology and improving the flexibility of automated configuration.

[0033] The automated configuration method provided in this application will be described in detail below.

[0034] See Figure 2 , Figure 2 This is a flowchart of an automated configuration method provided in this application. This method can be applied to an SDN controller, and the SDN controller implementing this method may include the following steps:

[0035] S201. Receive the automatic configuration instruction of the target network device, wherein the automatic configuration instruction carries the first timestamp of the target network device.

[0036] In this step, the SDN controller provides the user with a configuration entry point for automated configuration. The user can use the client to select the network device to be configured (denoted as the target network device), thereby triggering an automated configuration command for that target network device. To enable the SDN controller to perform automated configuration on the target network device subsequently, this automated configuration command can carry the target network device's first timestamp.

[0037] It is worth noting that the aforementioned first timestamp is reported to the SDN controller by the target network device through an interactive event. This interactive event can affect the topology data of the target network device in the global network topology. The SDN controller then feeds back the most recently received timestamp of the target network device to the client. For example, when a user sends a network topology query command to the SDN controller through the client, the SDN controller returns the currently queried global network topology to the client, and also feeds back the timestamps of the network devices corresponding to each topology node in the global network topology. The timestamp of each network device is reported to the SDN controller by the network device through an interactive event when it affects the topology data.

[0038] S202. When the target network device meets the configuration conditions, obtain the second timestamp of the target network device recorded locally.

[0039] In this step, after receiving the automatic configuration instruction for the target network device, the SDN controller can carry the device identifier of the target network device so that the SDN controller can determine whether the target network device is currently configurable based on the device identifier. Based on this, this application provides the above configuration conditions. Automatic configuration can only be performed when the target network device meets the above configuration conditions, that is, when the target network device is currently configurable.

[0040] Furthermore, when the target network device meets the configuration conditions, further processing is required. First, a second timestamp of the target network device is retrieved from the local records; this timestamp is the timestamp from the most recently received interaction event. Then, this second timestamp is compared with the first timestamp to confirm their similarity. If they are the same, it indicates that the target network device did not encounter any issues affecting its topology data after uploading the second timestamp, thus allowing for automated configuration. If they are different, it indicates that the target network device experienced issues affecting its topology data after reporting the first timestamp and reported an interaction event carrying the second timestamp to the SDN controller. In this case, the target network device is currently unstable and automated configuration cannot be performed temporarily to avoid problems during automated configuration.

[0041] S203. If the first timestamp is the same as the second timestamp, and the sub-network topology corresponding to the target network device is stable, then the target network device is automatically configured. The sub-network topology is the network topology consisting of the topology links to which the topology node corresponding to the target network device belongs, which is included in the global network topology currently recorded by the SDN controller.

[0042] In this step, when it is confirmed that the first timestamp and the second timestamp are the same, it indicates that the target network device has not caused any changes in the topology data. However, in order to achieve automated configuration of the target network device, in addition to the target network device being in a stable state, it is also necessary to ensure that the link where the target network device is located, that is, the sub-network topology formed by the topology link to which the topology node corresponding to the target network device belongs, is in a stable state. Therefore, this application proposes that the SDN controller can obtain the sub-network topology corresponding to the target network device, that is, a part of the global network topology mentioned above, and then determine whether the sub-network topology is in a stable state. When it is determined that it is in a stable state, it indicates that the target network device and its corresponding topology link are both stable, and the target network device can be automatically configured. At this time, the SDN controller can execute the automated configuration process for the target network device.

[0043] The automated configuration method provided in this application involves receiving an automated configuration instruction for a target network device, the instruction carrying a first timestamp of the target network device. When the target network device meets the configuration conditions, a second timestamp of the target network device recorded locally is obtained. If the first and second timestamps are the same, and the sub-network topology corresponding to the target network device is stable, then the target network device is automatically configured. In this application, before automatically configuring the target network device, the configurability of the target network device is determined. When it is currently configurable, the sub-network topology corresponding to the target network device is obtained. When the sub-network topology is determined to be stable, the target network device can be automatically configured. Since the sub-network topology is a network topology consisting of the topology links of the topology node corresponding to the target network device included in the global network topology currently recorded by the SDN controller, it is part of the global network topology. Therefore, even if the network topology other than the sub-network topology is unstable, it will not affect the configuration of the target network device. In other words, automated configuration of the target network device in a partially stable sub-network topology can be achieved even without global network topology stability, thereby improving the flexibility of automated configuration and enabling flexible responses to changes in network topology.

[0044] Optionally, based on any of the above embodiments, in this embodiment, topology nodes can be classified into nodes to be automated, already automated nodes, removed nodes, etc. The nodes to be automated refer to topology nodes that have not undergone automated configuration; the already automated nodes refer to topology nodes that have completed automated configuration, which may include automated configuration of topology links between adjacent nodes, and may also include automated configuration of the network device corresponding to the topology node itself; the removed nodes refer to nodes corresponding to network devices whose registration information has been removed from the SDN controller. Specific descriptions of each of the above nodes can be found in Table 1:

[0045] Table 1

[0046]

[0047] It should be noted that in practical applications, this classification can be further expanded, such as by adding a category for "non-existent nodes," to facilitate subsequent extended processing of automated configurations. The aforementioned "non-existent nodes" can refer to topology nodes where the registration information, topology data, and automation data are all absent.

[0048] The aforementioned automated nodes can be understood as follows: Taking the current network device corresponding to this node as an example, the current network device corresponding to this automated node has the following characteristics: if the port of the current network device has completed automated configuration with a port of the upstream network device, and the current network device itself has completed automated configuration.

[0049] Based on this, the method for determining whether the target network device meets the configuration conditions can be as follows: if it is confirmed that the target network device has a corresponding topology node in the global network topology, and the corresponding topology node is not a topology node that has been automatically configured or removed, then the target network device is determined to meet the configuration conditions.

[0050] Specifically, taking the target network device as Figure 1b Taking network device C in the network shown as an example, when a user triggers the above-mentioned automatic configuration command through a client, the automatic configuration command, in addition to carrying the first timestamp mentioned above, can also carry the device identifier of network device C. In this way, after obtaining the aforementioned device identifier, the SDN controller can determine whether a corresponding topology node exists for network device C in the global network topology, denoted as topology node C. If it exists, further judgment is performed, namely, whether the corresponding topology node C is an automated node and whether its automation configuration is consistent with the previous one. If both are true, it indicates that there is no need to automate it again, and network device C is confirmed not to meet the configuration conditions. If it is not an automated node, or if the current automation configuration for network device C is different from the previous automation configuration executed for network device C, it can further determine whether topology node C is currently a removed node, namely, whether the registration information of network device C exists in the records of the SDN controller, and whether the device automation data of network device C exists. If both exist, it is determined that topology node C is not a removed node, and thus network device C meets the configuration conditions. If at least one does not exist, it is determined that topology node C is a removed node, and thus network device C does not meet the configuration conditions.

[0051] It is worth noting that when the target network device meets the conditions for automated configuration, the following checks can be performed on its upstream network devices: whether a topology node corresponding to the upstream network device exists, and whether the topology node corresponding to the upstream network device is an automated node. If a topology node corresponding to the upstream network device exists, and the topology node corresponding to the upstream network device is not a removed node, and if the topology node corresponding to the upstream network device is an automated node, then it is determined that automated configuration can be performed on the target network device. Specifically, taking the target network device as an example... Figure 1b Taking network device C as an example, after determining that network device C is configurable, it is also possible to determine whether the upstream network device of network device C meets the above judgment conditions, that is, whether either network device D or network device E meets the above judgment conditions. When either network device meets the conditions, it indicates that network device C can be automatically configured.

[0052] It should be noted that if the topology node corresponding to the upstream network device of the target network device is a removed node, then since the upstream network device has corresponding topology data, it may not affect the automatic configuration of the target network device. That is, the automatic configuration of the target network device can still be completed at this time.

[0053] Based on this, if the upstream network device of the target network device has not performed automatic configuration, a first prompt message is output. The first prompt message is used to indicate that automatic configuration should not be enabled directly for the downstream network device of the upstream network device that has not performed automatic configuration.

[0054] Specifically, when the upstream network devices D and E of network device C are not automatically configured, it indicates that the communication connection between network device C and network devices D and E has not yet been established. Therefore, it is necessary to send a first prompt message to the client to display the above-mentioned first prompt message to the user. This first prompt message can be used to prompt the user to select network devices D and C, or network devices E and network devices C, when selecting the devices for automation, so as to better achieve automated configuration.

[0055] It is worth noting that, taking network device D as an example, when considering the upstream network device of network device C, if network device D has completed automatic configuration, it can mean that network device D itself has completed automatic configuration, and it can also mean that the ports between network device D and other downstream network devices other than network device C have also completed automatic configuration. Therefore, when automating network device C, it can include both the automatic configuration of network device C itself and the automatic configuration of the ports involved in the communication link between network device C and network device D.

[0056] Furthermore, if the ports involved in the link between network device D and network device C have been automatically configured, then when automatically configuring network device C, the automatic configuration instruction can be an instruction to instruct network device C to save the configuration.

[0057] In addition, when triggering automatic configuration, users can also select automatic configuration for two adjacent network devices at the same time. That is, when the target network device includes a first network device and a second network device, and the first network device is the upstream device of the second network device, the method for determining whether the target network device meets the configuration conditions can be as follows: if it is confirmed that the first network device and the second network device have corresponding topology nodes in the global network topology, and their respective topology nodes are neither topology nodes that have been automatically configured nor removed nodes, then the target network device is determined to meet the configuration conditions.

[0058] Furthermore, after both the first network device and the second network device meet the configuration conditions, the timestamp comparison process can be as follows: The above-mentioned automated configuration instruction carries the first timestamp of the first network device and the first timestamp of the second network device. Based on this, the SDN controller also needs to obtain the second timestamp of the first network device and the second timestamp of the second network device from the local machine respectively, and then determine whether the first timestamp and the second timestamp of the first network device are the same, and whether the first timestamp and the second timestamp of the second network device are the same. When they are all the same, the sub-network topology stability determination process is then executed.

[0059] Optionally, based on any of the above embodiments, in this embodiment, the method for determining the stability of the sub-network topology corresponding to the target network device can be executed according to the following process: if all the topology links to which the topology node corresponding to the target network device belongs are stable, then the sub-network topology corresponding to the target network device is determined to be stable.

[0060] Specifically, after obtaining the device identifier of the target network device, the current global network topology can be generated. Then, based on the device identifier, the global network topology is queried to determine the sub-network topology formed by the topology links of the topology nodes corresponding to the target network device. After that, the topology links of each topology node and the topology links between the topology nodes in the sub-network topology are traversed to identify whether the topology links are stable, and thus identify whether the sub-network topology is stable.

[0061] Alternatively, after obtaining the device identifier of the target network device, a sub-network topology can be directly generated, which includes the topology links of the topology nodes corresponding to the target network device. Then, the topology nodes and the topology links between the topology nodes in the sub-network topology are traversed to identify whether the topology links are stable, thereby identifying whether the sub-network topology is stable.

[0062] Before identifying the links, we will first introduce the categories of topology links. This embodiment proposes three types of topology links, including: changed links, automated links, and removed links. The changed links can be understood as links in which any of the upstream or downstream network devices involved has not been automatically configured. Automated links can be understood as links in which all network devices corresponding to the topology nodes on the link have been automatically configured, and the ports involved in the link have also been automatically configured. Removed links can be understood as links in which the link data has been removed.

[0063] For a detailed description, please refer to Table 2:

[0064] Table 2

[0065]

[0066] It should be noted that in practical applications, this classification can be further expanded, such as by adding a "no-link" category, to facilitate subsequent extended processing of automated configurations. The aforementioned "no-link" can refer to a topology link where neither the automated records nor the link data exist.

[0067] Based on this, when identifying whether a topology link is stable, it can be determined whether each topology node on the current topology link exists in the sub-network topology. If it exists, it is confirmed that the topology node is not offline, thus confirming that the topology link is stable, and therefore, automated configuration of the target network device can be performed. To better understand this embodiment, the target network device is used as an example. Figure 1b Taking network device C as an example, the sub-network topology corresponding to network device C can include topology link 1 between network device D and network device C, and / or topology link 2 between network device E and network device C. Based on this, if the SDN controller confirms that at least one of topology link 1 and topology link 2 is stable, it can determine that the sub-network topology is stable.

[0068] Based on this, the method to determine whether topology link 1 is stable can be as follows: After determining that network device C meets the configuration conditions, the SDN controller can continue to confirm whether network device D is in a down state. If network device D is not currently down and topology link 1 is not the aforementioned changed link, then topology link 1 can be determined to be stable.

[0069] Furthermore, when the topology link to which the topology node corresponding to the target network device belongs is a changing link, a second prompt message is output. The second prompt message is used to instruct the network devices at both ends of the link based on the topology link to perform automatic configuration.

[0070] Specifically, taking topology link 1 as an example, if topology link 1 is a changing link, that is, if network device D causes a change in topology data, then in order to achieve automated configuration of network device C, the SDN controller can send the aforementioned second prompt information to the client so that the user can perceive the change in topology link 1 through the second prompt information. Then, the network devices C and D at both ends of topology link 1 are selected for automated configuration together. This addresses the changes in the topology link and also enables automated configuration of the network devices.

[0071] Furthermore, if the target network devices are network devices C and D, then the sub-network topology is formed by topology link 1 corresponding to network devices D and C. In this case, the SDN controller can determine that the sub-network topology is stable when it confirms that topology link 1 is stable. Accordingly, the method for determining whether topology link 1 is stable can be: the SDN controller can determine that the network topology corresponding to topology link 1 is stable if it determines that both network devices C and D meet the configuration conditions.

[0072] Based on any of the above embodiments, in this embodiment, after the automatic configuration of the target network device is completed in step S203, the following process may also be included: when the sub-network topology includes removing nodes, and / or the sub-network topology includes removing links, then the automatic data of the network device corresponding to the removed node is deleted, and / or the topology data corresponding to the removed link is deleted.

[0073] Specifically, removing a node or link from the network topology does not affect the stability of the network topology. Therefore, when performing automated configuration on the target network device in the sub-network topology, the automated data of the removed node may be updated. Thus, after completing the automated configuration, the automated data corresponding to the removed node in the sub-network topology needs to be deleted to restore the state of the removed node before the automated configuration. Similarly, when performing automated configuration on the target network device in the sub-network topology, the topology data of the removed link may also be affected. Therefore, after completing the automated configuration, the topology data corresponding to the removed link in the sub-network topology needs to be deleted to restore the state of the removed link before the automated configuration. The aforementioned topology data may include, but is not limited to, link data, etc.

[0074] Based on any of the above embodiments, this embodiment also provides the following example: when the network device corresponding to the target topology node in the topology link goes offline, and the corresponding network device is not the target network device, the automation data and topology data of the corresponding network device remain unchanged.

[0075] Specifically, in a sub-network topology, there may be topology nodes corresponding to network devices that are offline. Figure 1b Taking the sub-network topology formed by network device C and network devices D and E respectively as an example, if network device E is offline but topology link 1 is stable, topology link 2 will become unstable, but the sub-network topology is stable. Therefore, when automatically configuring network device C, the automatic data and topology data of network device E should be kept unchanged to ensure that the state of the topology node of network device E in the global network topology is not affected.

[0076] Based on any of the above embodiments, this embodiment may also provide the following example: receiving a target network topology query command; outputting and feeding back the timestamps of the network devices corresponding to the topology nodes that have not completed automatic configuration and the topology nodes that have completed automatic configuration in the target network topology.

[0077] Specifically, the target network topology can be a part of the global network topology or the entire global network topology. When a user triggers a network topology query command through a client, the SDN controller can read the locally recorded automation data, and then traverse each topology node in the target network topology from the real-time topology memory based on the device identifier; determine the type of the topology node; if the topology node is a removed node, the timestamp of the network device corresponding to the removed node is not returned to the client; if the topology node is a non-automated node or an automated node, the timestamp of the network device corresponding to the topology node, i.e., the first timestamp, is returned to the client; when returning the timestamp, it can be returned by parameter assignment, such as assigning the value of the timestamp to the parameter used to represent the timestamp, and then returning the parameter value to the client. After traversing all the topology nodes of the target network topology, a target network topology with a tree structure is generated based on the neighbor relationships between the topology nodes, and returned to the client.

[0078] Optionally, based on any of the above embodiments, in this embodiment, the first timestamp and the second timestamp of the target network device are device timestamps or port timestamps, wherein the device timestamp is the timestamp at which the target network device generates data that affects the topology, and the port timestamp is the timestamp at which the port of the target network device generates data that affects the topology.

[0079] Specifically, the first timestamp of the target network device can be a device timestamp, that is, a device timestamp reported at the device level; of course, in order to perform more granular automated configuration, the first timestamp can also be a port timestamp, that is, after the target network device detects an event that causes a change in topology data on a certain port, it reports an interaction event to the SDN controller. The interaction event carries the port identifier of the port and the timestamp of the event that occurred on the port.

[0080] Accordingly, since the reported timestamps are for the ports, users can perform fine-grained queries when configuring target network devices. That is, the aforementioned sub-network topology is: the target topology link that uses this port to interact with other topology nodes within the topology link to which the topology node of the target network device belongs. Based on this, the process of determining whether the aforementioned sub-network topology is valid is then implemented.

[0081] This solves the problem of low configuration efficiency caused by the need to frequently refresh the entire global network topology before automating configuration when unstable nodes exist in the global network topology. Furthermore, this application performs automated configuration at the network device level, which can flexibly respond to changes in the global network topology and improve the flexibility of automated configuration.

[0082] Based on the same inventive concept, this application also provides an automated configuration device corresponding to the above-described automated configuration method. Specific implementation details of this automated configuration device can be found in the above description of the automated configuration method, and will not be elaborated upon here.

[0083] See Figure 3 , Figure 3 An automated configuration device provided in an exemplary embodiment of this application is disposed in an SDN controller. The device includes:

[0084] The receiving module 301 is used to receive an automatic configuration instruction for a target network device, wherein the automatic configuration instruction carries a first timestamp of the target network device;

[0085] The acquisition module 302 is used to acquire the second timestamp of the target network device recorded locally when the target network device meets the configuration conditions;

[0086] The configuration module 303 is used to automatically configure the target network device if the first timestamp is the same as the second timestamp and the sub-network topology corresponding to the target network device is stable. The sub-network topology is the network topology consisting of the topology links to which the topology node corresponding to the target network device belongs, which is included in the global network topology currently recorded by the SDN controller.

[0087] Optionally, the automated configuration device provided in this embodiment may further include:

[0088] The first determining module (not shown in the figure) is used to determine that the target network device meets the configuration conditions if it is confirmed that the target network device has a corresponding topology node in the global network topology, and the corresponding topology node is not a topology node that has been automatically configured or removed.

[0089] Furthermore, the above-mentioned device may also include:

[0090] The first output module (not shown in the figure) is used to output a first prompt message when the upstream network device of the target network device has not performed automatic configuration. The first prompt message is used to indicate that automatic configuration should not be enabled directly for the downstream network device of the upstream network device that has not performed automatic configuration.

[0091] Optionally, the automated configuration device provided in this embodiment may further include:

[0092] The second determining module (not shown in the figure) is used to determine that the sub-network topology corresponding to the target network device is stable if all the topology links to which the topology node to which the target network device belongs are stable.

[0093] Furthermore, the above-mentioned device may also include:

[0094] The deletion module (not shown in the figure) is used to delete the automated data of the network device corresponding to the removed node and / or the topology data corresponding to the removed link after the configuration module 303 completes the automated configuration of the target network device.

[0095] In addition, the above-mentioned device may also include:

[0096] The second output module (not shown in the figure) is used to output a second prompt message when the topology link to which the topology node corresponding to the target network device belongs is a changing link. The second prompt message is used to instruct the network devices at both ends of the link based on the topology link to perform automatic configuration.

[0097] Based on any of the above embodiments, the automated configuration device provided in this embodiment may further include:

[0098] The hold module (not shown in the figure) is used to keep the automation data and topology data of the corresponding network device unchanged when the network device corresponding to the target topology node in the topology link goes offline and the corresponding network device is not the target network device.

[0099] Based on any of the above embodiments, the automated configuration device provided in this embodiment may further include:

[0100] The receiving module (not shown in the figure) is used to receive the target network topology query command;

[0101] The feedback module (not shown in the figure) is used to output and feedback the timestamps of the network devices corresponding to the topology nodes that have not completed automatic configuration and the topology nodes that have completed automatic configuration in the target network topology.

[0102] Based on any of the above embodiments, in this embodiment, the first timestamp and the second timestamp of the target network device are device timestamps or port timestamps, wherein the device timestamp is the timestamp at which the target network device generates data that affects the topology, and the port timestamp is the timestamp at which the port of the target network device generates data that affects the topology.

[0103] This solves the problem of low configuration efficiency caused by the need to frequently refresh the entire global network topology before automating configuration when unstable nodes exist in the global network topology. Furthermore, this application performs automated configuration at the network device level, which can flexibly respond to changes in the global network topology and improve the flexibility of automated configuration.

[0104] Based on the same inventive concept, embodiments of this application provide an electronic device, which can be the aforementioned SDN controller, etc. Figure 4 As shown, the electronic device may include a processor 401 and a machine-readable storage medium 402. The machine-readable storage medium 402 stores a computer program executable by the processor 401. The processor 401 is prompted by the computer program to execute the automated configuration method provided in any embodiment of this application. Furthermore, the electronic device also includes a communication port 403 and a communication bus 404, wherein the processor 401, communication port 403, and machine-readable storage medium 402 communicate with each other via the communication bus 404.

[0105] The communication bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0106] The communication port is used for communication between the aforementioned electronic devices and other devices.

[0107] The machine-readable storage medium 402 described above can be a memory, which may include random access memory (RAM), DDR SRAM (Double Data Rate Synchronous Dynamic Random Access Memory), or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0108] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0109] For embodiments of electronic devices and machine-readable storage media, since the methods involved are basically similar to those described in the foregoing method embodiments, the description is relatively simple, and relevant details can be found in the descriptions of the method embodiments.

[0110] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0111] The specific implementation process of the functions and roles of each unit / module in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0112] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units / modules described as separate components may or may not be physically separate. The components shown as units / modules may or may not be physical units / modules, that is, they may be located in one place or distributed across multiple network units / modules. Some or all of the units / modules can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0113] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. An automated configuration method, characterized in that, The method, applied in an SDN controller, includes: Receive an automated configuration instruction for the target network device. The automated configuration instruction carries a first timestamp of the target network device. The first timestamp is the timestamp of the target network device reporting to the SDN controller via an interactive event, which is fed back to the client by the SDN controller. The interactive event can affect the topology data of the target network device in the global network topology. When the target network device meets the configuration conditions, the second timestamp of the target network device recorded locally is obtained. The second timestamp is the timestamp from the most recent interaction event received by the target network device. If the first timestamp is the same as the second timestamp, and the sub-network topology corresponding to the target network device is stable, then the target network device is automatically configured. The sub-network topology is the network topology consisting of the topology links to which the topology node corresponding to the target network device belongs, which is included in the global network topology currently recorded by the SDN controller. The method for determining whether the target network device meets the configuration conditions is as follows: If it is confirmed that the target network device has a corresponding topology node in the global network topology, and the corresponding topology node is not a topology node that has been automatically configured or removed, then the target network device is determined to meet the configuration conditions. The method for determining the stability of the subnetwork topology corresponding to the target network device is as follows: If all the topology links to which the topology node corresponding to the target network device belongs are stable, then the sub-network topology corresponding to the target network device is determined to be stable.

2. The method according to claim 1, characterized in that, When the upstream network device of the target network device has not performed automatic configuration, a first prompt message is output. The first prompt message is used to indicate that automatic configuration should not be enabled directly for the downstream network device of the upstream network device that has not performed automatic configuration.

3. The method according to claim 1, characterized in that, After completing the automated configuration of the target network device, the method further includes: When the sub-network topology includes removing a node, and / or when the sub-network topology includes removing a link, then delete the automation data of the network device corresponding to the removed node, and / or the topology data corresponding to the removed link.

4. The method according to claim 1, characterized in that, Also includes: When the topology link to which the topology node corresponding to the target network device belongs is a changing link, a second prompt message is output. The second prompt message is used to instruct the network devices at both ends of the link based on the topology link to perform automatic configuration.

5. The method according to claim 1, characterized in that, Also includes: When the network device corresponding to the target topology node in the topology link goes offline, and the corresponding network device is not the target network device, the automation data and topology data of the corresponding network device remain unchanged.

6. The method according to claim 1, characterized in that, Also includes: Receive the target network topology query command; The timestamps of the network devices corresponding to the topology nodes that have not completed automatic configuration and the topology nodes that have completed automatic configuration in the target network topology are output and fed back.

7. The method according to claim 1, characterized in that, The first and second timestamps of the target network device are device timestamps or port timestamps, wherein the device timestamp is the timestamp when the target network device generates an event that affects the topology data, and the port timestamp is the timestamp when the port of the target network device generates an event that affects the topology data.

8. An automated configuration device, characterized in that, The device, located in the SDN controller, includes: The receiving module is used to receive the automatic configuration instruction of the target network device. The automatic configuration instruction carries the first timestamp of the target network device. The first timestamp is the timestamp of the target network device reporting to the SDN controller through an interactive event, which is fed back by the SDN controller to the client. The interactive event can affect the topology data of the target network device in the global network topology. The acquisition module is used to acquire a second timestamp of the target network device that is locally recorded when the target network device meets the configuration conditions. The second timestamp is the timestamp from the most recent interaction event received by the target network device. The configuration module is used to automatically configure the target network device if the first timestamp is the same as the second timestamp and the sub-network topology corresponding to the target network device is stable. The sub-network topology is the network topology consisting of the topology links to which the topology node corresponding to the target network device belongs, which is included in the global network topology currently recorded by the SDN controller. The method for determining whether the target network device meets the configuration conditions is as follows: If it is confirmed that the target network device has a corresponding topology node in the global network topology, and the corresponding topology node is not a topology node that has been automatically configured or removed, then the target network device is determined to meet the configuration conditions. The method for determining the stability of the subnetwork topology corresponding to the target network device is as follows: If all the topology links to which the topology node corresponding to the target network device belongs are stable, then the sub-network topology corresponding to the target network device is determined to be stable.

Images