CN110166299B

CN110166299B - SDN controller configuration recovery method and device

Info

Publication number: CN110166299B
Application number: CN201910444606.7A
Authority: CN
Inventors: 沈珏萍
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Information Technologies Co Ltd
Priority date: 2019-05-24
Filing date: 2019-05-24
Publication date: 2022-05-10
Anticipated expiration: 2039-05-24
Also published as: CN110166299A

Abstract

The invention provides a method and a device for recovering configuration of an SDN controller. Relates to the technical field of software defined networking. Wherein, the method comprises the following steps: if a configuration module with abnormal configuration data exists on the SDN controller, determining a network device corresponding to the abnormal configuration module as a target network device; wherein the configuration module of the exception comprises: a basic configuration module and/or a service configuration module; acquiring original configuration data of the abnormal configuration module from the target network equipment; and applying the original configuration data of the abnormal configuration module to perform configuration recovery on the abnormal configuration module. According to the method and the device, the abnormal configuration module on the SDN controller is recovered by acquiring the original configuration data from the network equipment, so that the efficiency of configuration recovery is improved, the recovery time of the abnormal configuration module is shortened, and the stability of the network is improved.

Description

SDN controller configuration recovery method and device

Technical Field

The invention relates to the technical field of Software Defined networks, in particular to a Software Defined Network (SDN) controller configuration recovery method and device.

Background

SDN is a network architecture for network virtualization. The SDN mainly comprises an SDN controller and network equipment, and the configuration of the network equipment is realized by the SDN controller. However, due to constraints of communication cost, efficiency and the like, configuration data of the SDN controller and the network device are not always synchronized, which causes inconsistency of the configuration data between the SDN controller and the network device.

For example, the configuration data of the network device is deleted manually, the network device is restarted without storing the configuration data, or the network device is disconnected in the process of sending the configuration data by the SDN controller, and the SDN controller does not continue to send the configuration data to the network device after the network is restored. For another example, the configuration data of the SDN controller is unloaded by misoperation, the memory of the SDN controller has an error, and the like; these scenarios may all present configuration data inconsistencies of the SDN controller and the network device.

For the case that the configuration data of the SDN controller and the network device are not consistent, there may be a case that the network device has abnormal configuration data or a case that the SDN controller has abnormal configuration. If the network device has abnormal configuration, the current SDN controller may compare configuration data differences between the SDN controller and the network device through auditing and synchronize its own configuration to the network device, so as to recover the abnormal configuration data on the network device.

Disclosure of Invention

In view of this, the present invention provides a method and an apparatus for recovering configuration of an SDN controller, so as to improve efficiency of recovering configuration data.

In a first aspect, the present invention provides a method for recovering a configuration of an SDN controller. The method is applied to an SDN controller and comprises the following steps:

if a configuration module with abnormal configuration data exists on the SDN controller, determining network equipment corresponding to the abnormal configuration module as target network equipment;

wherein, the abnormal configuration module comprises: a basic configuration module and/or a service configuration module;

acquiring original configuration data of an abnormal configuration module from target network equipment;

and applying the original configuration data of the abnormal configuration module to perform configuration recovery on the abnormal configuration module.

In a second aspect, the present invention provides a method for recovering a configuration of an SDN controller. The method is applied to network equipment, and comprises the following steps:

receiving an acquisition instruction sent by an SDN controller;

and sending the original configuration data to the SDN controller according to the acquisition instruction so that the SDN controller applies the original configuration data to recover a configuration module with configuration data exception on the SDN controller.

In a third aspect, the present invention provides an SDN controller configuration recovery apparatus. The device is applied to the SDN controller and comprises:

a determining unit, configured to determine, if a configuration module with abnormal configuration data exists on the SDN controller, a network device corresponding to the abnormal configuration module as a target network device;

the acquisition unit is used for acquiring the original configuration data of the abnormal configuration module from the target network equipment;

and the recovery unit is used for applying the original configuration data of the abnormal configuration module to carry out configuration recovery on the abnormal configuration module.

In a fourth aspect, the present invention provides an SDN controller configuration recovery apparatus. The device is applied to network equipment and comprises:

a receiving unit, configured to receive an acquisition instruction sent by the SDN controller;

a sending unit, configured to send, according to the acquisition instruction, original configuration data to the SDN controller, so that the SDN controller applies the original configuration data to recover a configuration module with configuration data exception on the SDN controller.

In a fifth aspect, the present invention provides an SDN controller comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor executing the machine-executable instructions to implement the method of the first aspect.

In a sixth aspect, the present invention provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor executing the machine-executable instructions to implement the method of the second aspect.

In a seventh aspect, the present invention provides a machine-readable storage medium having stored thereon machine-executable instructions which, when invoked and executed by a processor, cause the processor to carry out the method of the first or second aspect.

According to the configuration recovery method and device for the SDN controller, provided by the embodiment of the invention, when the configuration module with abnormal configuration data appears on the SDN controller, the original configuration data is obtained from the network equipment to recover the abnormal configuration module on the SDN controller, so that the configuration recovery efficiency is improved, the consistency of the configuration data between the SDN controller and the network equipment is ensured, the time delay of manual configuration recovery on the SDN controller is relieved, and the stability of the network is further improved.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the invention as set forth above.

In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a diagram of a communication network architecture according to an embodiment of the present invention;

fig. 2 is a schematic flowchart of a method for recovering a configuration of an SDN controller according to an embodiment of the present invention;

fig. 3A is a schematic diagram illustrating a configuration command issuing method according to an embodiment of the present invention;

FIG. 3B is a schematic diagram illustrating another configuration command issue according to an embodiment of the present invention;

fig. 4 is a schematic flowchart of another SDN controller configuration recovery method according to an embodiment of the present invention;

fig. 5 is a schematic flowchart of another SDN controller configuration recovery method according to an embodiment of the present invention;

fig. 6 is a signaling interaction diagram of a method for recovering configuration of an SDN controller according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of an SDN controller configuration recovery apparatus according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of another SDN controller configuration recovery apparatus according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of another SDN controller according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a network device according to an embodiment of the present invention.

Detailed Description

To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The embodiment of the invention provides a method and a device for recovering configuration of an SDN controller, which can be applied to a network constructed based on an SDN, for example, refer to a possible communication network architecture diagram shown in FIG. 1: SDN controller 110 and network device 120 may be included in the communication network. The network device 120 may be an access device, a gateway device, a firewall device, a load balancing device, and the like, and the network device 120 may include one or more devices. Among other things, SDN controller 110 may communicate with network device 120 to enable controlling network device 120. For example, SDN controller 110 may perform configuration operations on network device 120 by issuing configuration data.

In one example, the SDN controller 110 and the network device 120 communicate with each other through a network configuration protocol (NETCONF), which is a configuration management protocol of a new generation of network devices. The SDN controller may add, modify, and delete configuration data of the network device 120 through the NETCONF mechanism, obtain configuration data and state information of the network device 120, and the like. The NETCONF network device 120 may provide a standardized Application Programming Interface (API), and in this embodiment of the present invention, the SDN controller 110 may directly use the API to send and obtain configuration data to the network device 120. NETCONF employs a client/server (C/S) structure, the SDN controller 110 serves as a NETCONF client, the network device 120 serves as a NETCONF server, and the SDN controller 110 can perform management operations such as configuration on the network device 120 through the NETCONF.

Configuration data on SDN controller 110 may include basic configuration data and service configuration data, and the like, where the basic configuration data and the service configuration data are respectively of multiple types, and different types of configuration data may be used differently, for example, different types of configuration data may be used for configuring different types of network devices, or different types of configuration data may be used for configuring different functions of the same network device. To facilitate management, SDN controller 110 may implement management of different types of configuration data through different configuration modules.

In some embodiments, as shown in fig. 1, the SDN controller 110 may include two major types, namely a basic configuration module 111 and a service configuration module 112, where the basic configuration module 111 and the service configuration module 112 are relative, for example, the basic configuration module 111 and the service configuration module 112 may be a basic configuration module and a service configuration module of a first network, and may also be a basic configuration module and a service configuration module of a second network, where the first network is formed by at least one network device, and the second network is a virtual network created based on the first network.

Because configuration data managed on the SDN controller is more and complicated, if the configuration data of the SDN controller 110 is abnormal, for example, the configuration data in the SDN controller 110 is missing or wrong, the administrator needs to consume more manpower and material resources for reconfiguration, and the longer the abnormal configuration data is recovered, the lower the stability of the network is. Based on this, the embodiment of the present invention provides a method and an apparatus for recovering configuration of an SDN controller, which can recover, when configuration data on the SDN controller is abnormal, original configuration data on a network device corresponding to the abnormal configuration module, so as to improve efficiency of configuration recovery, reduce time for configuration recovery, and improve stability of a network.

In the embodiment of the present invention, the above configuration recovery refers to recovering an abnormal configuration module to a normal configuration module, for example, adding missing configuration data on the configuration module or modifying wrong configuration data on the configuration module.

Fig. 2 is a schematic flowchart of a method for recovering a configuration of an SDN controller according to an embodiment of the present invention. The method is applied to an SDN controller, and as shown in fig. 2, the method specifically includes the following steps:

and S210, if the configuration module with abnormal configuration data exists on the SDN controller, determining the network device corresponding to the abnormal configuration module as a target network device.

Wherein, the abnormal configuration module may include: a basic configuration module and/or a service configuration module.

In some embodiments, the abnormal configuration module includes a basic configuration module and/or a service configuration module of the second network. The basic configuration module can comprise a virtual link layer network configuration module, a virtual router configuration module and the like; the traffic configuration module may include firewall configuration data, load balancing configuration data, and the like.

The virtual link layer configuration module may be configured to configure an access device;

the virtual router configuration module may be configured to configure a gateway device;

the firewall configuration module can be used for configuring firewall equipment;

the load balancing configuration module may be used to configure a load balancing device, and the like.

In addition, the network devices that the same type of base configuration module or service configuration module is used to configure may include one or more, for example, the virtual link layer configuration module may be used to configure one or more access devices.

Therefore, the network device corresponding to the abnormal configuration module can be determined according to the configuration relationship between the configuration module and the network device. And the network equipment corresponding to the abnormal configuration module is used as target network equipment to acquire original configuration data.

Configuration data of a configuration module on the SDN controller may include configuration items and configuration parameters corresponding to the configuration items, and the like. For example, the configuration items of the Virtual router configuration module may include a Virtual Private Network (VPN), a three-Layer Virtual extended Local Area Network identifier (Layer 3Virtual Extensible Local Area Network, l3vni), and the like; the VPN configuration item corresponds to a VPN configuration parameter, which may be 10002 specifically; the l3vni configuration item corresponds to the l3vni parameter, which may be 10008 specifically.

The configuration module with abnormal configuration data may include abnormal configuration items, abnormal configuration parameters, or abnormal configuration items and configuration parameters of the configuration module, and may also include lost configuration modules, deleted configuration modules with errors, or error configuration modules.

S220, acquiring the original configuration data of the abnormal configuration module from the target network equipment.

The original configuration data may refer to the configuration data of the abnormal configuration module before the abnormality. When the network device is configured by the SDN controller, the SDN controller needs to send configuration data before an abnormality to the network device, and the configuration data before the abnormality received by the network device may be considered as original configuration data of an abnormal configuration module.

In one example, the raw configuration data received by the network device may be a configuration command. For example, the abnormal configuration module is a virtual router configuration module. The configuration data of the virtual router configuration module before the exception is the parameter of the configuration item VPN is 10002, and the parameter of the configuration item l3vni is 10008. The SDN controller may generate a configuration command through the virtual router configuration module before the abnormality, and issue the configuration command to the gateway device, where the configuration command may be considered as original configuration data of the virtual router configuration module after the abnormality occurs. For example, the configuration command issued to the gateway device may be: the interface to be configured is "virtual switch interface (vsi) 3"; the configuration command is described as "SDN-vsi-10008"; configuring the IP-VPN to be "10002"; configure l3vni to "10008"; after the virtual router configuration module is abnormal in configuration data, the SDN controller may obtain the configuration command from the network device as original configuration data of the virtual router configuration module.

And S230, applying the original configuration data of the abnormal configuration module to perform configuration recovery on the abnormal configuration module.

According to the method provided by the embodiment of the invention, when the configuration module with abnormal configuration data appears on the SDN controller, the target network equipment corresponding to the abnormal configuration module is determined, the original configuration data is obtained from the target network equipment, and the abnormal configuration module on the SDN controller is recovered by taking the original configuration data as a reference, so that the abnormal configuration module is recovered in time, the consistency of the configuration data between the SDN controller and the network equipment is ensured, the time delay of manually recovering the abnormal configuration module on the SDN controller is relieved, and the networking stability based on the SDN is further improved.

In order to make the various types of configuration data well distinguishable, the configuration modules may be pre-configured with configuration module identifiers for distinguishing from each other, for example, the configuration module identifier may be "Virtual Router (VROUTE) _", and the "VROUTE _" is a Virtual Router configuration module identifier; as another example, the configuration module identification may be "FIREWALL (FIREWALL) _" which is a FIREWALL configuration module identification.

When sending configuration data (e.g., a configuration command) to a network device, the SDN controller may carry a configuration module identifier of a configuration module corresponding to the configuration data to identify which configuration module the configuration data belongs to, for example: the configuration data corresponding to the virtual link layer network module carries a virtual link layer network configuration module identifier, and the configuration data is usually sent to the access device; the configuration data corresponding to the virtual router configuration module carries a virtual router configuration module identifier, and the configuration data is usually issued to the gateway device; the configuration data corresponding to the firewall configuration module carries the firewall configuration module identifier, and the configuration data is usually sent to the firewall device. Therefore, the corresponding network device can be determined based on the current abnormal configuration module, and after the network device is taken as the target network device, the original configuration data corresponding to the abnormal configuration module can be acquired from the target network device by using the configuration module identifier.

For example, as shown in connection with fig. 3A, SDN controller 310 may include a virtual router configuration module, and an intrusion prevention system configuration module for configuring a network device whose device type is a firewall. The SDN controller 310 may include a virtual router configuration module 311, a firewall configuration module 312, and an intrusion-prevention system (IPS) configuration module 313, based on which the SDN controller 310 may send configuration commands 321, 322, and 323 to the firewall device 320. Wherein, the configuration command 321 includes a configuration module identifier "VROUTE _"; configuration command 322 includes a configuration module identification "FIREWALL"; the configuration command 323 includes a configuration module identification "SDN _ IPS _".

For another example, as shown in fig. 3B, the SDN controller 330 includes a firewall configuration module configured to configure the network device with a firewall device type, and a load balancing configuration module configured to configure the network device with a load balancing device type. The SDN controller 330 may include a firewall configuration module 331 and a load balancing configuration module 332, and based on the above configuration relationship, the SDN controller 330 may send a configuration command 341 to the firewall device 340 and a configuration command 351 to the load balancing device 350. Wherein, the configuration command 341 includes a configuration module identifier "FIREWALL _"; configuration command 351 includes a configuration module identification of "S load balancing _".

To better indicate that the configuration data are all from the SDN controller, a specific identifier, such as "SDN _" or "SDN/" may be added to the configuration module identifier, and the identifier of the module itself is added after the specific identifier, such as the module identifier of the firewall module may be specifically expressed as: the SDN _ FIREWALL indicates that the configuration data is configuration data issued by the FIREWALL module and belongs to a service type if the configuration data carries the SDN _ FIREWALL, and if the configuration data is restored, the original configuration data can be acquired from the FIREWALL device and restored by using the acquired original configuration data corresponding to the FIREWALL module.

In some embodiments, since there may be many configuration data on the network device, the SDN controller may include multiple acquisition modes when acquiring the raw configuration data.

Example (1), the above S220 may be implemented at least by the following steps:

sending a first acquisition instruction to target network equipment, wherein the first acquisition instruction carries a first command identifier;

receiving all original configuration data which are sent by target network equipment according to a first command identifier and are locally stored by the target network equipment, wherein each configuration data in all the original configuration data carries a configuration module identifier;

and selecting the original configuration data of the abnormal configuration module from all the original configuration data according to the configuration module identification of the abnormal configuration module.

Example (2), the above S220 may be implemented at least by the following steps:

sending a second acquisition instruction to the target network equipment, wherein the second acquisition instruction carries a second command identifier and a configuration module identifier of the abnormal configuration module;

and receiving the original configuration data of the abnormal configuration module sent by the target network equipment according to the second command identifier and the configuration module identifier of the abnormal configuration module.

For example (1) or (2), in order to better distinguish which configuration module the configuration data sent by the network device belongs to when the original configuration data is obtained, the configuration data sent by the SDN controller to the network device may carry the configuration module identifier.

For example, the SDN controller sends a configuration command to the network device, where the configuration command may be in a format of extensible markup language (XML), the configuration command may include information such as a configuration name, a description, configuration items, and parameters, the configuration name may include a configuration module identifier, or the description may include the configuration module identifier. For another example, the SDN controller issues the configuration command of the gateway device as "SDN-VROUTE-vsi-10008", or the SDN controller issues the configuration command of the gateway device includes that the interface to be configured is "VROUTE-vsi 3", where "VROUTE" is the router configuration module identifier.

For example (1), the target network device may select, according to the abnormal configuration module identifier and the configuration module identifier carried in the configuration command, the configuration command including the abnormal configuration module identifier from all the configuration commands, and use the configuration command as the original configuration data of the abnormal configuration module, and send the original configuration data of the abnormal configuration module to the SDN controller.

For example (2) above, the target network device may return all configuration commands stored locally, and the SDN controller may select, according to the configuration module identifier of the exception and the configuration module identifier carried in the configuration command, the configuration command including the configuration module identifier of the exception from all configuration commands, as original configuration data of the exception configuration module.

In addition, as for the above-described example (1) or (2), the first command identifier and the second command identifier may be the same identifier or different identifiers.

In one example, the first command identifier and the second command identifier may be the same identifier, where the first command identifier or the second command identifier is used to instruct the target network device to return the original configuration data, and if the obtaining instruction does not include the configuration module identifier, that is, does not specify which configuration module to return the original configuration data, the target network device returns all the original configuration data; if the obtaining instruction contains the configuration module identifier, that is, the original configuration data indicating which configuration module to return to, the target network device returns the original configuration data corresponding to the configuration module identifier.

In another example, the first command identifier and the second command identifier may be different command identifiers, where the first command identifier is used to instruct the target network device to return all original configuration data, and the second command identifier is used to instruct the target network device to return original configuration data corresponding to the configuration module identifier carried in the acquisition instruction.

By the method for acquiring the original configuration data, the corresponding original configuration data can be found according to the abnormal configuration module, and then the abnormal configuration module is recovered according to the original configuration data in a targeted manner, so that the accuracy of acquiring the original configuration data is ensured, and the recovery efficiency is improved.

In practical applications, the configuration module for determining whether the SDN controller has the configuration data exception may be implemented by at least one of the following manners:

the method comprises the following steps that (1), when an abnormal configuration recovery instruction is received, a configuration module indicated by the abnormal configuration recovery instruction is determined to be an abnormal configuration module;

in the method (2), when the configuration module is detected to have configuration data loss, the configuration module with the configuration data loss is determined as an abnormal configuration module;

in the mode (3), when the configuration data error exists on the abnormal configuration module, the configuration module with the error configuration data is determined as the abnormal configuration module.

For the above manner (1), in an example of the configuration module that determines whether there is an exception on the SDN controller, the configuration module that determines whether there is an exception by receiving an instruction triggered by a user, where the user may be an administrator of the SDN controller. For example, when a user finds that configuration data is abnormal, an abnormal configuration data recovery instruction may be triggered, where the abnormal configuration data recovery instruction may carry a configuration module identifier, and the abnormal configuration recovery instruction is used to indicate that a configuration module corresponding to the configuration module identifier has a configuration data abnormality, so that after receiving the abnormal configuration recovery instruction, the SDN controller determines the configuration module indicated by the abnormal configuration recovery instruction as an abnormal configuration module. The configuration module identifier may include a type identifier of configuration data corresponding to the configuration module, an identifier or other identifiers of the configuration module, and the like.

With regard to manners (2) and (3) above, in another example of a configuration module that determines whether configuration data is abnormal on the SDN controller, the SDN controller may detect configuration data of a local configuration module. For example, a loss, error, or uninstallation of configuration data may be detected. For example, when it is detected that a parameter corresponding to a configuration item (e.g., l3vni or VPN) in configuration data of a configuration module is lost, or the configuration data is deleted by mistake or unloaded by mistake, it is determined that the configuration module is an abnormal configuration module.

Through any of the above manners (1) to (3), it can be determined that the configuration module with abnormal configuration data exists on the SDN controller, and in this case, the configuration recovery method provided by the present invention can be used for recovery, so as to implement a configuration recovery process based on the original configuration data on the network device. In practical application, if configuration data is abnormal on the network device, the configuration data can be recovered by taking the configuration data on the SDN controller as a reference.

In practical applications, network topology data of a network device on the SDN controller may also be abnormal. At this time, before the above S210, the following steps may be further included:

if the network topology data of the network equipment on the SDN controller is abnormal, the network topology data of the network equipment on the SDN controller is recovered firstly.

In the above steps, recovering the network topology data on the SDN controller may be performed by receiving a network topology data recovery instruction triggered by a user.

For example, a user may select a network device that needs to establish a network topology through the SDN controller and trigger a network topology restoration instruction for the selected network device. As another example, the SDN controller may provide a user interface corresponding to the management network topology, which may display connectable network devices; based on the user interface, the user configures network equipment needing to establish a topological relation, such as an IP address, a user name and a password of NETCONF connection and the like; and after receiving the network topology recovery instruction aiming at the network equipment and input by a user, the SDN controller establishes NETCONF connection with the network equipment.

The above configuration modules may have mutual dependency relationship, and if configuration data of a plurality of configuration modules is abnormal, the process configuration may be recovered based on the mutual dependency relationship among the abnormal configuration modules.

In some embodiments, the configuration module of the exception may include a plurality of modules, and in this case, S230 may be implemented by: the SDN controller may apply raw configuration data of a plurality of anomalous configuration modules. And sequentially carrying out configuration recovery on each abnormal configuration module according to a preset configuration sequence.

Wherein, the preset configuration sequence comprises: the basic configuration module has priority over the order of the service configuration modules, and the order of the configuration dependency relations among different basic modules or among different service configuration modules.

For example, the preset configuration sequence may be that a virtual subnet is configured first, then a virtual link layer network is configured, and then the virtual router is bound to the virtual subnet, where the virtual subnet is configured by a virtual subnet configuration module, the virtual link layer network is configured by a virtual link layer network configuration module, and the virtual router is bound to the virtual subnet by a virtual router configuration module; the virtual subnet configuration module, the virtual link layer network configuration module and the virtual router configuration module all belong to the basic configuration module. When the configuration is recovered, the virtual subnet configuration module has priority over the virtual link layer network configuration module, and the virtual link layer network configuration module has priority over the virtual router configuration module.

In addition, the above-mentioned applying the original configuration data of the plurality of abnormal configuration modules, and sequentially performing configuration recovery on each abnormal configuration module according to the preset configuration sequence may at least include the following modes:

example (1), if the abnormal configuration module is a part of all configuration modules on the SDN controller, a current abnormal configuration module may be selected from the plurality of abnormal configuration modules according to a preset configuration order, and an original configuration item and an original parameter corresponding to the current abnormal configuration module are generated by applying original configuration data corresponding to the current abnormal configuration module; and applying the original configuration item and the original parameter corresponding to the current abnormal configuration module to carry out configuration recovery on the current abnormal configuration module.

Example (2), if the abnormal configuration module is all the configuration modules on the SDN controller, the current abnormal configuration module may be selected from the multiple abnormal configuration modules according to a preset configuration order, and the original configuration data corresponding to the current abnormal configuration module is applied to generate an original configuration item and an original parameter corresponding to the current abnormal configuration module; generating a configuration database file by applying the original configuration items and the original parameters corresponding to all the configuration modules; and performing configuration recovery by applying the configuration database file according to a preset configuration sequence.

In some embodiments, the SDN controller, when configuring the network device, may configure according to configuration data received from a user.

For example, the SDN controller may provide a user configuration interface corresponding to the configuration module, and a user may input configuration items and parameters corresponding to the configuration items based on the user configuration interface. And the SDN controller generates a configuration command according to the received user input configuration item and the corresponding parameter, and issues the configuration command to the network equipment to realize the configuration of the network equipment.

For another example, the SDN controller may provide a user interface corresponding to the virtual router configuration module, where the user interface includes a configuration item VPN and a configuration item l3vni, each configuration item corresponds to an entry field, and the user may enter parameters in the entry field, for example, enter 10002 in the entry field corresponding to the configuration item VPN, and enter 10008 in the entry field corresponding to the configuration item l3 vni.

TABLE 1

The SDN controller may also generate a data table according to the correspondence between the received configuration items and the parameters, for example, the data table shown in table 1 may be generated based on the entered information. The corresponding relationship between the configuration item and the parameter is generally stored in the operating memory, and the data table is generally stored in the local storage. Each configuration module may correspond to multiple data tables, and after the SDN controller is restarted, configuration data of each configuration module may be generated according to the data tables. When recovering the abnormal configuration module, the abnormal configuration module needs to be recovered, corresponding to the data table on the local storage and the configuration items and parameters in the operating memory.

In example (1) above, based on the configuration process, when the configuration recovery is implemented, the SDN controller may recover only the data table corresponding to the abnormal configuration module and the configuration data in the running memory. For example, the original configuration data may be a configuration command that is: the interface that needs to be configured is "vsi 3"; the description of the configuration command is "SDN-VROUTE-vsi-10008"; configuring the IP-VPN to be "10002"; set l3vni to "10008" (or, the interface that needs to be configured is "VROUTE-vsi 3"). According to the configuration command, the description is SDN _ VROUTE, and the configuration parameters corresponding to the configuration items vpn and l3vni are obtained, so that a configuration parameter data table can be generated as shown in table 2. Based on this table 2, the virtual router configuration module can be configured to be restored.

TABLE 2

In some embodiments, when the original configuration data of the abnormal configuration module is applied and the configuration of the abnormal configuration module is recovered, the method may be implemented by at least the following steps:

receiving a configuration recovery rule selected based on a preset configuration recovery rule alternative list;

step (2), applying the original configuration data of the abnormal configuration module, and performing configuration recovery on the abnormal configuration module according to the selected configuration recovery rule;

wherein the configuration recovery rule comprises one or more of:

adding missing configuration data on the abnormal configuration module;

deleting excessive configuration data on the abnormal configuration module;

modifying the conflicting configuration data on the anomalous configuration module;

conflicting configuration data is maintained on the anomalous configuration module.

In one example, the configuration restoration rules may include an append mode that may include adding missing configuration data compared to the original configuration data without deleting existing configuration data of the SDN controller.

In another example, the configuration restoration rules may also include an overlay mode. The overlay mode may include completely recovering from the original configuration data, or the conflicting configuration data may be from the configuration data on the SDN controller, and the non-conflicting configuration data may be from the original configuration data.

step (1), determining the auditing difference of the abnormal configuration module by using the original configuration data of the abnormal configuration module;

and (2) recovering the abnormal configuration data of the abnormal configuration module by taking the original configuration data of the abnormal configuration module as a reference according to the audit difference of the abnormal configuration module.

In addition, the SDN controller may backup configuration data of the configuration module. For example, the backup may be performed periodically or manually, and if an abnormal configuration module exists on the SDN controller, the configuration recovery may be performed through the backup.

In some embodiments, the abnormal configuration modules of the SDN controller may be restored to the last backup first. And then proceeds to S210-S230. In S230, the original configuration data may be applied to restore the abnormal configuration module restored according to the backup.

Based on the embodiment, a proper mode can be selected as required to carry out configuration recovery according to the original configuration data of the abnormal configuration module, so that the configuration recovery is more reasonable, and the stability of the network is improved.

Fig. 4 is a schematic flowchart of another SDN controller configuration recovery method according to an embodiment of the present invention. The method is applied to a network device, and as shown in fig. 4, the method may specifically include the following steps:

and S410, receiving an acquisition instruction sent by the SDN controller.

The "fetch instruction" in this step may be the first fetch instruction in the embodiment shown in fig. 2 described above, or the second fetch instruction.

As can be known from the foregoing embodiment shown in fig. 2, the SDN controller may issue a first obtaining instruction for obtaining all configuration data to the network device, where the first obtaining instruction may include a first command identifier, and after receiving the first obtaining instruction, the network device determines all configuration data from the SDN controller.

The SDN controller may also issue, to the network device, a second acquisition instruction for acquiring the original configuration data of the abnormal configuration module, where the second acquisition instruction may include a second command identifier and an abnormal configuration module identifier, and after receiving the second acquisition instruction, the network device determines the original configuration data of the abnormal configuration module.

In some embodiments, the first command identifier and the second command identifier may be the same identifier, or may be different command identifiers, which may specifically refer to the description of the foregoing embodiments, and are not described herein again.

And S420, sending original configuration data to the SDN controller according to the acquisition instruction so that the SDN controller applies the original configuration data to recover a configuration module with configuration data exception on the SDN controller.

If the SDN controller issues the first acquisition instruction, the network device needs to determine all configuration data from the SDN controller. And sending all the original configuration data to the SDN controller according to the first command identifier, wherein each configuration data in all the original configuration data carries a configuration module identifier.

If the SDN controller issues a second acquisition instruction to the network device, determining original configuration data of an abnormal configuration module according to a configuration module identifier carried by the second acquisition instruction; and sending the abnormal original configuration data of the configuration module to the SDN controller according to the second command identifier carried by the second acquisition instruction.

For the SDN controller to recover the abnormal configuration data on the SDN controller by applying the original configuration data, reference may be made to the related description in step S230 in the embodiment shown in fig. 2, which is not described herein again.

According to the embodiment of the invention, when the SDN controller has the abnormal configuration module, the network device can provide the SDN controller with the original configuration data corresponding to the abnormal configuration module, so that the SDN controller can recover the abnormal configuration module, thereby realizing mutual backup of the SDN controller and the network device and improving the stability of networking based on the SDN.

Fig. 5 is a flowchart illustrating another SDN controller configuration recovery method according to an embodiment of the present invention. As shown in fig. 5, the following steps may be specifically referred to:

step (1), the SDN controller receives an instruction for configuration recovery from the network equipment.

The instruction for configuration recovery from the network device may include a configuration module identifier, and it may be determined that the configuration module corresponding to the configuration module identifier is an abnormal configuration module.

Step (2), the SDN controller determines network topology data; based on the network topology data, the original configuration data can be obtained from the target network device corresponding to the abnormal configuration module.

The network topology data may include connection relationships between network devices 1 to n (n is an integer greater than 0) and the SDN controller.

In the step (2), "determining network topology data" is an optional step, if the network topology data is not abnormal, the step of "determining network topology data" is not required to be executed, and if the target network device in the network topology data is disconnected, the step of "determining network topology data" and the disconnected target network device need to be executed to reestablish connection.

Based on the network topology data, the SDN controller may send a fetch instruction to the target network device to fetch the original configuration data of the abnormal configuration module. For this step, reference may be specifically made to the foregoing description in the embodiment shown in fig. 2, and relevant descriptions in step S210 and step S220 are not described herein again.

And (3) recovering the SDN controller based on one mode selected from the overlay mode and the additional mode.

The coverage modes are also divided into two types, namely, the controller configuration is taken as the standard when the conflict exists, and the equipment configuration is taken as the standard when the conflict exists. Specifically, which mode is selected needs to be selected by an administrator according to configuration requirements.

In step (3), "overlay mode" and "add mode" can refer to the foregoing embodiment shown in fig. 2, and the description about "overlay mode" and "add mode" is not repeated here.

And (4) recovering the abnormal configuration modules one by one according to a preset configuration sequence by applying the original configuration data by the SDN controller.

The preset configuration sequence can be determined according to the dependency relationship among the configuration modules. In one example, when configuring the second configuration module, the first configuration module is configured first, and then the second configuration module depends on the first configuration module, and when recovering, the first configuration module is recovered first according to the dependency relationship, and then the second configuration module is recovered, for example, the first configuration module may be a basic configuration module, and the second configuration module may be a service configuration module. Specifically, the first configuration module is recovered by using the original configuration data acquired from the network device corresponding to the first configuration module, and the second configuration module is recovered by using the original configuration data acquired from the network device corresponding to the second configuration module.

Fig. 6 is a signaling interaction diagram of a method for recovering a configuration of an SDN controller according to an embodiment of the present invention. An interaction flow between an SDN controller and a terminal device on a network device is illustrated, which may be specifically executed with reference to the following steps:

and S601, the SDN controller determines a configuration module with local configuration data exception.

S602, the SDN controller determines a target network device corresponding to the abnormal configuration module.

And S603, the SDN controller sends an acquisition instruction to the target network equipment.

S604, the network device sends the original configuration data to the SDN controller.

And S605, the SDN controller applies the original configuration data of the abnormal configuration module to perform configuration recovery on the abnormal configuration module.

Step S601 may refer to the related description about determining that there is abnormal configuration data on the SDN controller in the embodiment shown in fig. 2, step S602 may refer to the related description about step S210 in the embodiment shown in fig. 2, step S603 may refer to the related description about sending the original configuration data acquisition instruction to the target network device in the embodiment shown in fig. 2, step S604 may refer to the related description about returning the original configuration data to the SDN controller in the embodiment shown in fig. 4, and step S605 may refer to the related description about step S210 in the embodiment shown in fig. 2, which is not described again here.

Fig. 7 is a schematic structural diagram of an SDN controller configuration recovery apparatus according to an embodiment of the present invention. The device is applied to an SDN controller. The device may specifically comprise the following units:

a determining unit 701, configured to determine, if a configuration module with abnormal configuration data exists on the SDN controller, a network device corresponding to the abnormal configuration module as a target network device; wherein the configuration module of the exception comprises: a basic configuration module and/or a service configuration module;

an obtaining unit 702, configured to obtain, from the target network device, original configuration data of the abnormal configuration module;

a recovering unit 703, configured to apply the original configuration data of the abnormal configuration module to perform configuration recovery on the abnormal configuration module.

In some embodiments, the obtaining unit 702 is specifically configured to:

sending a first acquisition instruction to the target network equipment, wherein the first acquisition instruction carries a first command identifier;

receiving all original configuration data which are sent by the target network equipment according to the first command identifier and are locally stored by the target network equipment, wherein each configuration data in all the original configuration data carries a configuration module identifier;

In some embodiments, the obtaining unit 702 is specifically configured to:

sending a second acquisition instruction to the target network device, wherein the second acquisition instruction carries a second command identifier and the configuration module identifier of the abnormal configuration module;

and receiving the original configuration data of the abnormal configuration module, which is sent by the target network equipment according to the second command identifier and the configuration module identifier of the abnormal configuration module.

In some embodiments, the configuration module of the exception comprises a plurality of modules; the recovery unit 703 is specifically configured to:

applying original configuration data of a plurality of abnormal configuration modules, and sequentially performing configuration recovery on each abnormal configuration module according to a preset configuration sequence;

wherein the preset configuration sequence comprises: the basic configuration module has priority over the order of the service configuration modules, and the order of the configuration dependency relations among different basic modules or among different service configuration modules.

In some embodiments, the recovery unit 703 is specifically configured to:

applying the original configuration data of the abnormal configuration module, and performing configuration recovery on the abnormal configuration module according to a selected configuration recovery rule;

the configuration restoration rules include one or more of:

adding missing configuration data on the abnormal configuration module;

deleting excessive configuration data on the abnormal configuration module;

modifying conflicting configuration data on the anomalous configuration module;

In some embodiments, the recovery unit 703 is specifically configured to:

determining the auditing difference of the abnormal configuration module by applying the original configuration data of the abnormal configuration module;

and recovering the abnormal configuration data of the abnormal configuration module by taking the original configuration data of the abnormal configuration module as a reference according to the audit difference of the abnormal configuration module.

In some embodiments, the method further comprises:

when an abnormal configuration recovery instruction is received, determining a configuration module indicated by the abnormal configuration recovery instruction as a configuration module with abnormal configuration data; or;

when detecting that the configuration module has configuration data loss, determining the configuration module losing the configuration data as a configuration module with configuration data abnormity; or;

when detecting that the configuration data exist on the configuration module in error, determining the configuration module with the configuration data in error as the configuration module with the configuration data exception.

Fig. 8 is a schematic structural diagram of an SDN controller configuration recovery apparatus according to an embodiment of the present invention. The device is applied to network equipment, and the device comprises:

a receiving unit 801, configured to receive an acquisition instruction sent by the SDN controller;

a sending unit 802, configured to send original configuration data to the SDN controller according to the obtaining instruction, so that the SDN controller applies the original configuration data to recover a configuration module with a configuration data exception on the SDN controller.

In some embodiments, the obtaining instruction includes a first command identifier, and the sending unit 802 is specifically configured to:

sending all original configuration data to the SDN controller according to the first command identifier, wherein each configuration data in all the original configuration data carries a configuration module identifier.

In some embodiments, the obtaining instruction includes a second command identifier and a configuration module identifier of the abnormal configuration module;

further comprising: the determining unit is used for determining the original configuration data of the abnormal configuration module according to the configuration module identification of the abnormal configuration module;

the sending unit 802 is specifically configured to send, to the SDN controller, the original configuration data of the abnormal configuration module according to the second command identifier.

Fig. 9 is a schematic structural diagram of an SDN controller according to an embodiment of the present invention, where the SDN controller includes: a processor 1100, a memory 1101, a bus 1102 and a communication interface 1103, the processor 1100, the communication interface 1103 and the memory 1101 being connected by the bus 1102; the processor 1100 is configured to execute executable modules stored in the memory 1101, such as computer programs corresponding to the method embodiments shown in fig. 2 or fig. 5.

Fig. 10 is a schematic structural diagram of a network device according to an embodiment of the present invention, where the network device includes: a processor 1200, a memory 1201, a bus 1202, and a communication interface 1203, the processor 1200, the communication interface 1203, and the memory 1201 being connected by the bus 1202; the processor 1200 is configured to execute an executable module stored in the memory 1201, for example, a computer program corresponding to the method embodiment shown in fig. 4.

The Memory in fig. 9 or fig. 10 may include a high-speed Random Access Memory (RAM) and may further include a non-volatile Memory (e.g., at least one disk Memory). The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network and the like can be used.

The bus may be an ISA bus, PCI bus, EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in fig. 9 or 10, but this does not indicate only one bus or one type of bus.

The memory is used for storing a program, and the processor executes the program after receiving an execution instruction, and the method executed by the apparatus defined by the flow process disclosed in any of the foregoing embodiments of the present invention may be applied to or implemented by the processor.

The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component. The various methods, steps and logic blocks disclosed in this disclosure may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the present invention may be embodied directly in a hardware decoding processor, or in a combination of hardware and software modules within the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

Embodiments of the present invention further provide a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions, and when the machine-executable instructions are called and executed by a processor, the machine-executable instructions cause the processor to implement the SDN controller configuration recovery method provided by the embodiments of the present invention.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Finally, it should be noted that: although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. An SDN controller configuration recovery method is applied to an SDN controller, and comprises the following steps:

if a configuration module with abnormal configuration data exists on the SDN controller, determining a network device corresponding to the abnormal configuration module as a target network device; wherein the configuration module of the exception comprises: a basic configuration module and/or a service configuration module; the basic configuration module at least comprises a virtual link layer network configuration module and a virtual router configuration module, and the service configuration module is at least used for configuring firewall configuration data and load balancing configuration data;

acquiring original configuration data of the abnormal configuration module from the target network equipment;

2. The method of claim 1, wherein the obtaining the raw configuration data of the abnormal configuration module from the target network device comprises:

3. The method of claim 1, wherein obtaining raw configuration data of the anomalous configuration module from the target network device comprises:

4. The method according to any one of claims 1 to 3, wherein the abnormal configuration module comprises a plurality; the applying the original configuration data of the abnormal configuration module to perform configuration recovery on the abnormal configuration module includes:

5. The method according to claim 1, wherein the applying the original configuration data of the abnormal configuration module to perform configuration recovery on the abnormal configuration module comprises:

the configuration restoration rules include one or more of:

adding missing configuration data on the abnormal configuration module;

deleting excessive configuration data on the abnormal configuration module;

modifying conflicting configuration data on the anomalous configuration module;

6. The method according to claim 1, wherein the applying the original configuration data of the abnormal configuration module to perform configuration recovery on the abnormal configuration module comprises:

7. The method of claim 1, wherein before determining the network device corresponding to the abnormal configuration model as the target network device, further comprising:

8. A method for recovering configuration of an SDN controller is applied to a network device, wherein the network device is a network device corresponding to an abnormal configuration module if the configuration module with abnormal configuration data exists on the SDN controller; wherein the configuration module of the exception comprises: a basic configuration module and/or a service configuration module; the basic configuration module at least comprises a virtual link layer network configuration module and a virtual router configuration module, and the service configuration module is at least used for configuring firewall configuration data and load balancing configuration data;

the method comprises the following steps:

receiving an acquisition instruction sent by the SDN controller;

sending original configuration data to the SDN controller according to the acquisition instruction so that the SDN controller applies the original configuration data to recover a configuration module with configuration data exception on the SDN controller.

9. The method of claim 8, wherein the obtaining instructions comprise a first command identifier, and wherein sending raw configuration data to the SDN controller according to the command identifier comprises:

10. The method of claim 8, wherein the fetch instruction comprises a second command identification and a configuration module identification of the anomalous configuration module;

the sending all raw configuration data to the SDN controller according to the obtaining instruction includes:

determining the original configuration data of the abnormal configuration module according to the configuration module identification of the abnormal configuration module;

and sending the original configuration data of the abnormal configuration module to the SDN controller according to the second command identification.

11. An SDN controller configuration recovery device applied to an SDN controller, the device comprising:

a determining unit, configured to determine, if a configuration module with abnormal configuration data exists on the SDN controller, a network device corresponding to the abnormal configuration module as a target network device; wherein the configuration module of the exception comprises: a basic configuration module and/or a service configuration module; the basic configuration module at least comprises a virtual link layer network configuration module and a virtual router configuration module, and the service configuration module is at least used for configuring firewall configuration data and load balancing configuration data;

an obtaining unit, configured to obtain, from the target network device, original configuration data of the abnormal configuration module;

12. An SDN controller configuration recovery device is applied to a network device, wherein the network device is a network device corresponding to an abnormal configuration module if the configuration module with abnormal configuration data exists on an SDN controller; wherein the configuration module of the exception comprises: a basic configuration module and/or a service configuration module; the basic configuration module at least comprises a virtual link layer network configuration module and a virtual router configuration module, and the service configuration module is at least used for configuring firewall configuration data and load balancing configuration data;

the device comprises: