CN114422336A

CN114422336A - Control plane debugging method, device, node and storage medium

Info

Publication number: CN114422336A
Application number: CN202111577777.0A
Authority: CN
Inventors: 万达; 马涛; 何胜元; 郭芬; 高进军; 梅岚翔; 王玺霖
Original assignee: Sangfor Technologies Co Ltd
Current assignee: Sangfor Technologies Co Ltd
Priority date: 2021-12-22
Filing date: 2021-12-22
Publication date: 2022-04-29

Abstract

The application discloses a control plane debugging method, a device, a node and a storage medium, wherein the method comprises the following steps: determining first configuration information from a first database; configuring a data plane network element based on the first configuration information; after configuring the data plane network element based on the first configuration information, performing fault location on the first control plane; the first database stores configuration information which is acquired by the node by calling the first control plane and issued by a management plane network element of a network where the node is located. In the above scheme, based on the configuration information sent by the management plane network element acquired by the first control plane, the first node calculates and configures the data plane network element, so that the replay process of configuration calculation and sending is realized, and the first control plane is subjected to fault location in the process, thereby improving the accuracy and efficiency of fault location of the control plane.

Description

Control plane debugging method, device, node and storage medium

Technical Field

The present application relates to the field of network technologies, and in particular, to a method, an apparatus, a node, and a storage medium for debugging a control plane.

Background

With the rising of technologies such as cloud computing, big data, mobile networks and Internet of Things (IoT), application programs are increasingly diversified, and the requirements on network functions are higher and higher. In this case, a Software Defined Network (SDN) is created, which is a technology for separating a Control Plane (CP) of a Network device from a Data Plane (DP), and realizes Control of Network traffic. In the related art, when the SDN is in a problem, the fault location efficiency of the control plane is not high.

Disclosure of Invention

In view of this, embodiments of the present application provide a method, an apparatus, a node, and a storage medium for debugging a control plane, which can improve the efficiency of fault location of the control plane.

The technical scheme of the embodiment of the application is realized as follows:

the embodiment of the application provides a control plane debugging method, which is applied to a first node and comprises the following steps:

determining first configuration information from a first database;

configuring a data plane network element based on the first configuration information;

after configuring the data plane network element based on the first configuration information, performing fault location on a first control plane; wherein the content of the first and second substances,

the first database stores configuration information which is acquired by the node by calling the first control plane and issued by a management plane network element of a network where the node is located.

In the foregoing solution, before the determining the first configuration information from the first database, the method further includes:

receiving second configuration information and writing the second configuration information into the first database; wherein the content of the first and second substances,

the second configuration information represents configuration information which is acquired by the second node by calling the first control plane and is issued by a management plane network element of a network where the second node is located.

In the foregoing solution, the receiving the second configuration information includes:

and receiving the second configuration information input by a user.

and receiving the second configuration information sent by the second node.

acquiring third configuration information by calling the first control plane, and writing the third configuration information into the first database; the third configuration information represents configuration information issued by a management plane network element of a network where the first node is located.

In the above scheme, the network where the first node is located further includes a first cluster; the first cluster represents a cluster for storing configuration information issued by a management plane network element; the obtaining of the third configuration information by invoking the first control plane includes:

obtaining the third configuration information from the first cluster by invoking the first control plane.

In the above scheme, the configuration information stored in the first database is encoded configuration information; the determining the first configuration information from the first database includes:

and decoding the corresponding configuration information in the first database to obtain the first configuration information.

The embodiment of the present application further provides a control plane debugging device, including:

the processing unit is used for determining first configuration information from the first database;

a configuration unit, configured to configure a data plane network element based on the first configuration information;

the query unit is used for carrying out fault positioning on the first control plane after the data plane network element is configured based on the first configuration information; wherein the content of the first and second substances,

The embodiment of the present application further provides a node, which includes: a processor and a memory for storing a computer program capable of running on the processor,

the processor is configured to execute any of the above steps of the control plane debugging method when running the computer program.

The embodiment of the present application further provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method implements the steps of any one of the above-mentioned control plane debugging methods.

In the embodiment of the application, a first node determines first configuration information from a first database, and configures a data plane network element based on the first configuration information; after configuring the data plane network element based on the first configuration information, performing fault location on the first control plane; the first database stores configuration information which is acquired by calling the first control plane and issued by a management plane network element of a network where the node is located. In the above scheme, based on the configuration information sent by the management plane network element acquired by the first control plane, the first node calculates and configures the data plane network element, so as to realize the replay process of configuration calculation and configuration sending, and perform fault location on the first control plane in the replay process, without calculating the configuration of the data plane sent by the control plane according to the flow of the data plane, thereby improving the fault location efficiency of the control plane; and moreover, the fault location accuracy of the control plane is improved by reproducing the fault site of the control plane.

Drawings

Fig. 1 is a schematic diagram of a control plane architecture according to an embodiment of the present application;

fig. 2 is an application diagram of a control plane architecture according to an embodiment of the present application;

fig. 3 is a schematic diagram of an implementation flow of a control plane debugging method provided in the embodiment of the present application;

fig. 4 is a schematic flow chart illustrating an implementation of a control plane debugging method according to another embodiment of the present application;

fig. 5 is a schematic flow chart illustrating an implementation of a control plane debugging method according to another embodiment of the present application;

fig. 6 is a schematic flow chart of data saving provided in an application embodiment of the present application;

FIG. 7 is a schematic flowchart of playback provided by an embodiment of the present application;

fig. 8 is a schematic structural diagram of a control plane debugging apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a node according to an embodiment of the present application.

Detailed Description

With the rise of technologies such as cloud computing, big data, mobile networks, IoT and the like, application programs are increasingly diversified, networks need to bear huge traffic, requirements on network functions are higher and higher, and network structures become more and more complex. For example, in a cloud computing scenario, a network is required to have high scalability; in a big data scenario, the network capacity demand of a data center shows a continuous and rapid increase; in a mobile network, a large amount of complex traffic such as pictures and videos can be generated, and a great burden is brought to enterprises providing network services; in an IoT scenario, a network needs to carry huge traffic generated by IoT terminals such as smart homes, car networking, smart cities, and the like. Moreover, with the increasing network bandwidth and the decreasing network delay, a large amount of multimedia data traffic such as voice, data, and video is collected in the network, making the traffic pattern more difficult to predict. In the face of the ever increasing complexity, dynamics and diversity of traffic, traditional network architectures are becoming increasingly unsuitable.

In this case, SDN comes from the birth, which is a technology for separating a control plane and a data plane of a network device, and realizes control of network traffic. Management, control and forwarding of SDNs are logically separated, called Management Plane (MP), CP and DP, respectively. Wherein the control plane CP is further divided into a local control plane LCP and a central control plane CCP. The SDN separates the control and the forwarding of the network equipment through software, forwarding strategies are managed and issued in a centralized mode through separated controllers, and the lower-layer data forwarding can be flexibly controlled through the controllers. After the transfer control is separated, the control plane is in the core position, the control plane controls the forwarding plane (namely, the data plane) through programming, and the core function of the network is realized through the control plane.

When the SDN is in problem, the fault location efficiency of the control plane is not high.

Based on this, in various embodiments of the present application, the first node determines first configuration information from the first database, and configures the data plane network element based on the first configuration information; after configuring the data plane network element based on the first configuration information, performing fault location on the first control plane; the first database stores configuration information which is acquired by calling the first control plane and issued by a management plane network element of a network where the node is located. In the above scheme, based on the configuration information sent by the management plane network element acquired by the first control plane, the first node calculates and configures the data plane network element, so as to realize the replay process of configuration calculation and configuration sending, and perform fault location on the first control plane in the replay process, without calculating the configuration of the data plane sent by the control plane according to the flow of the data plane, thereby improving the fault location efficiency of the control plane; and moreover, the fault location accuracy of the control plane is improved by reproducing the fault site of the control plane.

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The control plane debugging method of the embodiments of the present application can be used for various control plane architectures of SDNs.

Fig. 1 is a schematic diagram of a control plane architecture according to an embodiment of the present disclosure. The Control Plane architecture includes an MP, a northbound Kafka cluster, a Central Control Plane (CCP) cluster, a southbound Kafka cluster, and a Local Control Plane (LCP).

MP: the MP manages various network elements (virtual switches, virtual routers, etc.) and provides interfaces to users, such as Application Programming Interfaces (APIs), User Interfaces (UIs), etc., to the north. Various network elements and corresponding topology configurations are sent southbound to the CCP in the form of configuration messages over the Kafka message channel. The user configuration can be maintained inside the MP according to a relational database (such as MySQL and the like) and the consistency is ensured.

Northbound Kafka cluster: the northbound Kafka cluster is the message channel between the MP and the CCP. The northbound Kafka cluster configuration has only one Topic (Topic) comprising N partitions (Partition), each of which may consist of M copies (Replica). Each Tenant (Tenant) maps uniquely to one partition, each containing configuration messages for K tenants. Each tenant message in each partition is ordered.

CCP clustering: the CCP cluster is composed of a plurality of CCPs, and is a part that stores complete network configuration information in a control plane and calculates a network topology. The CCP communicates with the MP through a northbound message middleware Kafka cluster, the MP issues network configuration to the northbound Kafka cluster, the CCP pulls the network configuration from the northbound Kafka cluster, and the CCP performs relevant scheduling calculation on the pulled network configuration and then issues the network configuration to topic of different southbound Kafka.

The CCP consumes northbound Kafka data rules. All CCPs were in the same Kafka consumption Group (Consumer Group). Each northbound Kafka partition is uniquely mapped to a central controller CCP. Each CCP is responsible for processing messages in multiple northbound Kafka partitions. Thus, each tenant's messages are handled by only one CCP; each CCP processes messages for multiple tenants.

CCP produces southward Kafka data rules. Each CCP processes the northbound Kafka data, generates data and writes the data into the Redis storage cluster, calculates a physical node host group to which network configuration (generated data) should be issued, finds out all corresponding southbound Kafka themes according to the mapping relation between the tenant to which the message belongs and the host, and broadcasts the data to the themes. Here, the mapping relationship is mainly determined according to the physical host location of the network element to which the configuration belongs and the corresponding relationship between the physical host and the theme. For example, a routing rule is sent to a virtual router vr-a, the route runs on a host A, the corresponding subject of the host A is topic-a, and the mapping relation is that a message sent to vr-a needs to be sent to topic-a.

Redis storage cluster: the Redis storage cluster is composed of at least one Redis node and stores network configuration information. Redis clusters use Hash slots (Hash Slot) for data fragmentation. Each hash slot maps uniquely to one Redis node. Redis uses a master-slave mode to realize high availability, and each hash slot corresponds to one master node and a plurality of slave nodes. The CCP writes data such as network configuration and the like into the Redis, the CCP records system states and coordinates among each other through the Redis, and the LCP pulls required configuration from the Redis according to calculation requirements (for example, reference relation of the configuration).

Southbound Kafka clusters: the southbound Kafka cluster is the message channel between CCP and LCP. The southbound Kafka cluster is configured with M topics, one partition per topic, and each partition may consist of N replicas. Each local controller LCP maps to a southbound Kafka consumption Group (Consumer Group). The data of each partition is read by K local controllers LCP.

LCP: processing the southward Kafka message queue message, pulling network configuration from the southward Kafka cluster and Redis, calculating scheduling, accessing the Redis to pull the latest configuration, constructing a virtual network topology, calculating configuration according to the network topology, converting data into data plane recognizable data, and forwarding the data plane. The LCP is an agent installed on each host node in the control plane, and is responsible for receiving and processing CCP messages, interacting with the DP, and reporting host network information.

DP: and the virtual network forwarding module is responsible for virtual network forwarding and forwarding the data packet from the virtual machine to a physical network port or a virtual network port of other virtual machines.

Kafka is an open-source message middleware, is a high-throughput distributed publish-subscribe message system, and can be operated as a cluster on one or more servers which can span multiple data centers. The Kafka cluster stores the record streams in categories called topics and makes a backup of the copy for each topic according to the configuration. Each record in Kafka contains a key, a value, and a timestamp.

Redis (remote Dictionary Server): the remote dictionary service is an open source log-type and Key-Value database which is written by using ANSI C language, supports network, can be based on memory and can also be persistent, and provides API of multiple languages.

Fig. 2 shows an application schematic diagram of a control plane architecture provided in an embodiment of the present application, which supports at least one of the following network configuration distribution methods:

in a network configuration distribution method, an MP sends various network elements and corresponding topology configurations to a CCP in the form of configuration messages through a northbound Kafka cluster. And the CCP judges whether the Redis data needs to be read or not according to the specific content of the configuration, calculates according to the configuration message and the existing network configuration, updates the configuration and writes the updated configuration into the Redis cluster. The CCP calculates a broadcast domain, sends configuration updating configuration information to the LCP through the south-to-Kafka cluster, the LCP receives the configuration information sent by the CCP through the south-to-Kafka cluster, judges whether the association configuration needs to be pulled from the Redis cluster or not based on the configuration information, and stores the pulled configuration in a local cache and sends the configuration updating and all the association configuration to a configuration database of a data plane if the association configuration needs to be pulled from the Redis cluster.

In another network configuration distribution method, the MP sends various network elements and corresponding topology configurations to the CCP in the form of configuration messages through the northbound Kafka cluster. The CCP sends a message to the Redis cluster to enable the Redis cluster to be disconnected with all LCPs, and the LCP detects that the connection with the Redis cluster is disconnected due to the fact that the LCP and the Redis cluster have heartbeats, and starts to detect whether configuration information needs to be pulled or not. The CCP pulls configuration information from north to the Kafka cluster for calculation, and writes full configuration information to the Redis cluster. The CCP writes the LCP Start full Sync flag to the Redis cluster. LCP detects LCP starting full synchronous mark in Redis cluster, determines configuration information needed to be pulled, pulls configuration data from Redis cluster, and sends configuration update and all associated configuration to configuration database of data plane.

The following describes in detail the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems by embodiments and with reference to the drawings. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.

Fig. 3 is a schematic view of an implementation flow of a control plane debugging method provided in an embodiment of the present application, which is applied to a first node, where the first node includes, but is not limited to, an electronic device such as a server and a terminal.

The control plane debugging method shown in fig. 3 is applied to a first node, and includes:

step 301: first configuration information is determined from a first database.

The first database stores configuration information which is acquired by calling the first control plane and issued by a management plane network element of a network where the node is located.

The first database of the first node stores configuration information which is acquired by calling the first control plane and issued by a management plane network element of a network where the node is located, and the configuration information in the first database has a corresponding relation with the first control plane. And under the condition of fault location of the first control plane or other fault location needing to be carried out, the first node determines the first configuration information from the first database. The first configuration information may represent configuration information issued when the management plane network element configures the data plane network element one or more times.

The first database may be a local database, and the database resides in the first node, and the first node may read data from the first database as needed. And the first database plays a role in storing the configuration information issued by the management plane network element, records the configuration information issued by the management plane network element each time the data plane network element is configured, and can replay the processes of configuration calculation and configuration issue based on the configuration information in the first database. Preferably, the first database may function to save transient data in the memory to the storage device, and to persistently store the configuration information, wherein the first database is still able to save the configuration information therein when the LCP process is closed. The first configuration information is associated with constructing the first topology and may be used to construct the first topology.

Here, the source of the configuration information stored in the first database of the first node includes, but is not limited to: the first node acquires the information sent by a management plane network element of a network where the first node is located; the other nodes acquire and dump to the first node. That is to say, the configuration information stored in the first database of the first node may not be obtained by the first node calling the first control plane, but may be transferred to the first node after other nodes call the first control plane, and at this time, the first node may play a role in debugging data of the control plane.

The first node is not limited to an electronic device in the network, and may be an independent electronic device. The first node may obtain the configuration information through data import.

Step 302: and configuring the data plane network element based on the first configuration information.

The first node configures the data plane network element at least once based on the corresponding first configuration information, so that at least one configuration processing process of the first control plane can be replayed, that is, the process of performing configuration calculation and configuration issue on the first control plane based on the configuration information sent by the management plane network element is replayed.

Therefore, based on the first configuration information, the configuration calculation and configuration issuing process of the corresponding first control plane can be replayed, and the fault location of the first control plane is realized.

Step 303: and after configuring the data plane network element based on the first configuration information, performing fault location on the first control plane.

The first configuration information and the first control plane have a corresponding relationship, and the first control plane is a control plane corresponding to the management plane network element when issuing the configuration information of the configuration data plane network element. The node obtains the configuration information issued by the management plane network element by calling the first control plane, and configures the data plane network element based on the configuration information.

After configuring the data plane network element, the first node may perform fault location on the first control plane through one or more debugging means such as an information collection tool, query of a control plane log, and breakpoint debugging. Here, the information collection tool may collect configuration files, log files, and information of the system while running, query control plane data information, and/or determine state information of the control plane. Based on the information collected by the information collecting tool, the method can help to locate problems in the network and carry out fault location on the control plane. The fault location may be a bug location for the control plane; the queried status information includes, but is not limited to: data content of the control plane, controller state, component state, and/or system resource usage.

In practical applications, when performing control plane debugging on the control plane architecture shown in fig. 1, the information collection tool used may be Sdn-cli, which is a central control plane and local control plane command line tool. The operating state data of the central control plane and the local control plane can be queried using Sdn-cli.

It should be noted that, before step 303, step 301 and step 302 may be executed multiple times, that is, after the configuration calculation and the playback process of the configuration issue are implemented multiple times, the status information of the first control plane is queried. Thus, the configuration information of the first database supports replaying the entire process of configuration calculation and configuration issue of the control plane when managing the plane configuration data plane within any period of time.

In each embodiment of the application, based on configuration information acquired by a first control plane and sent by a management plane network element, a first node calculates and configures a data plane network element, so that a replay process of configuration calculation and configuration sending is realized, and fault location is performed on the first control plane in the replay process, the configuration of the data plane sent by the control plane is not required to be calculated according to the flow of the data plane, and the fault location efficiency of the control plane is improved; and moreover, the fault location accuracy of the control plane is improved by reproducing the fault site of the control plane.

As mentioned above, the source of the configuration information stored in the first database of the first node may be obtained and transferred to the first node by other nodes.

Fig. 4 is a schematic view of an implementation flow of another control plane debugging method provided in the embodiment of the present application, which is applied to a first node, where the first node includes, but is not limited to, an electronic device such as a server and a terminal.

The control plane debugging method shown in fig. 4 is applied to a first node, and includes:

step 401: and receiving second configuration information, and writing the second configuration information into the first database.

And the second configuration information represents configuration information which is acquired by the second node by calling the first control plane and is issued by a management plane network element of a network where the second node is located.

The second node obtains second configuration information by calling the first control plane, and the second configuration information is issued to the second node by a management plane network element of a network where the second node is located. And the second node sends second configuration information to the first node, and the first node receives the second configuration information of the second node and writes the second configuration information into the first database. The second configuration information may represent configuration information issued when the management plane network element configures the data plane network element one or more times.

Here, the first node may receive the second configuration information in case of fault location of the first control plane or other situations requiring fault location; it may be that the second node receives configuration information of the management plane network element to the data plane network element each time. The condition for the first node to receive the second configuration information is not limited herein.

The second node may process the received at least one piece of second configuration information into a corresponding compressed packet, send the second configuration information in the form of a compressed packet, and decompress the compressed packet by the first node to obtain the at least one piece of second configuration information.

Preferably, each time the second node obtains the second configuration information, the second configuration information is stored in a second database, and the second database stores the second configuration information obtained by the second node each time.

The second node represents a node different from the first node, and the second node and the first node may be in the same network environment or in different network environments, which is not limited herein. In practical application, nodes of a control plane architecture are usually deployed in at least two network environments, such as an experimental environment and a user environment, so that debugging tools in the experimental environment are more abundant, and a control plane can be debugged more efficiently in the experimental environment; meanwhile, the configuration information of the second node is received through the first node, and the configuration information of the second node in different environments is imported into the first node, so that offline debugging of the control plane is supported, and offline positioning of faults is realized.

In some embodiments, the receiving second configuration information comprises:

and receiving the second configuration information input by a user.

And the second node derives the acquired second configuration information, and then the user inputs the second configuration information into the first node. Therefore, direct communication between the first node and the second node is not needed, offline debugging of the control plane is supported, and offline positioning of faults is realized; meanwhile, the network security of the network where the node is located can be guaranteed.

In some embodiments, the receiving second configuration information comprises:

and receiving the second configuration information sent by the second node.

And the second node sends the acquired second configuration information to the first node. Therefore, the efficiency of acquiring the configuration information by the second node is improved, and the fault positioning efficiency of the control plane is improved.

Step 402: first configuration information is determined from a first database.

Step 402 is the same as step 301, and please refer to the related description in step 301 for the implementation process.

It should be noted that the first database of the first node stores the configuration information, which is obtained by the second node by calling the first control plane and issued by the management plane network element of the network where the second node is located, and the configuration information in the first database has a corresponding relationship with the first control plane. In practical application, the second node may be any node loaded with LCP in fig. 1, in other words, the second node may implement corresponding function by loading LCP.

Step 403: and configuring the data plane network element based on the first configuration information.

Step 403 is the same as step 302, and please refer to the related description in step 302 for the implementation process.

Step 404: and after configuring the data plane network element based on the first configuration information, performing fault location on the first control plane.

Step 404 is the same as step 303, and please refer to the related description in step 303 for the implementation process.

In the foregoing, the source of the configuration information stored in the first database of the first node may be issued by the first node when acquiring the management plane network element of the network where the first node is located.

Fig. 5 is a schematic view of an implementation flow of another control plane debugging method provided in an embodiment of the present application, which is applied to a first node, where the first node includes, but is not limited to, an electronic device such as a server and a terminal.

Step 501: and acquiring third configuration information by calling the first control plane, and writing the third configuration information into the first database.

Wherein the third configuration information represents configuration information issued by a management plane network element of a network where the first node is located.

The first node acquires third configuration information by calling the first control plane, and the third configuration information is issued to the first node by a management plane network element of a network where the first node is located. And the first node writes the acquired third configuration information into the first database. The third configuration information may represent configuration information issued when the management plane network element configures the data plane network element one or more times.

The first node obtains third configuration information issued when the management plane network element configures the data plane network element for one time or multiple times by calling the first control plane, and writes the third configuration information into a first database local to the first node, so that the first node can perform fault location on the control plane of the network where the first node is located.

Preferably, each time the first node obtains the third configuration information, the third configuration information is stored in the first database, and the third configuration information obtained by the first node each time is stored in the first database.

As mentioned above, the control plane debugging method of the embodiments of the present application can be used for various control plane architectures of SDNs. In some embodiments, the network in which the first node is located further comprises a first cluster; the first cluster represents a cluster for storing configuration information issued by a management plane network element; the obtaining of the third configuration information by invoking the first control plane includes:

In the control plane architecture shown in fig. 1, the first node represents an LCP node, and when the management plane network element issues the third configuration information to the LCP node, the first cluster may represent a southbound Kafka cluster and/or a Redis cluster according to a specific network configuration distribution method. In practical application, the first node may be any node loaded with the LCP in fig. 1, in other words, the first node may implement a corresponding function by loading the LCP.

Here, the first node acquires the third configuration information, which is stored in the first cluster by the management plane network element, by calling the first control plane, that is, the LCP.

Step 502: first configuration information is determined from a first database.

Step 503: and configuring the data plane network element based on the first configuration information.

Step 504: and after configuring the data plane network element based on the first configuration information, performing fault location on the first control plane.

Step 504 is the same as step 303, and please refer to the related description in step 303 for the implementation process.

In some embodiments, the configuration information stored in the first database is encoded configuration information; the determining the first configuration information from the first database includes:

The configuration information stored in a first database of the first node is encoded, the first database stores the configuration information in at least one record, and when the first configuration information needs to be determined, the configuration information is decoded based on the corresponding record in the first database to obtain the first configuration information. Thus, the management of the configuration information is realized through the coding and decoding of the configuration information.

As shown in fig. 1, in the control plane architecture, CCP and LCP need to perform a large amount of scheduling calculation, so the architecture design of the control plane is complex, and the debugging difficulty of the control plane architecture is high. Common traffic replay tools, such as tcprep and TcpCopy, replay traffic sent to a data plane based on a control plane, and only reverse the configuration sent to the data plane by the control plane from the data plane traffic, but cannot directly reproduce the bug site (fault site) of the control plane, and thus the debugging efficiency of the control plane is not high.

The control plane architecture shown in fig. 1 is taken as a specific scenario, and the present application is further described in detail with reference to an application embodiment.

The application embodiment of the application is provided with a replay module (replay), an encoding module (encode), a decoding module (decode) and a cache data storage module (db) of the control plane, which respectively realize corresponding functions, and realize the replay function based on the modules.

A replay module: and the data management module is responsible for importing the Kafka and Redis data, encoding the Kafka and Redis data and exporting the encoded Kafka and Redis data to db, and importing the db module data and replaying the db module data to the data plane.

The coding module: and coding and converting the configuration data cached by the control plane into a db data format.

A decoding module: and decoding the data record in the db, converting the data record into a data format which can be conveniently processed by the data plane dp module api, wherein the data format of the forwarding plane dp is established by an api interface provided by the forwarding plane dp module.

A data caching module: the data is responsible for storing control plane cache data, and the data format is shown in a cache data module structure diagram in table 1. The data of the control plane is network configuration, and the network configuration information comprises configuration ID, configuration type, operation type, configuration position and main body information of the rest configurations. The data is stored by a local database of the node.

TABLE 1DB data record Structure

key	value
		Entity_id	Configuration ID
Entity_type	Type of configuration
		operation	Operation type, update operation value is update, delete operation value is delete
location	Configuring the location to which the host belongs, and setting the value as the entry _ id configured by the host to which the host belongs
		info	Configured subject information

The application embodiment of the application is realized by two parts, namely a data storage flow and a replay flow.

Fig. 6 is a schematic flow chart illustrating data saving provided by an application embodiment of the present application, where a node may export Kafka and Redis data of a client field environment through a Kafka official data export command and a Redis official data export command using a set information collection tool. And importing the data into a replay module of the control plane, judging whether the data comes from the DB module by the replay module, if not, indicating that the data comes from Kafka/Redis, importing the data into an encode module for encoding, and storing the encoded data into the DB module, wherein the data is stored in the DB module.

The set information collecting tool can collect configuration files, log files and information of the system during operation, query control plane data information and/or determine state information of the control plane. The information collected by the set information collecting tool can help to locate the problems in the network conveniently.

Here, the replay module determines whether the data is from the DB module, and may determine whether the data carries a setting identifier, and if the data carries the setting identifier, the data is considered to be from the DB module.

Fig. 7 is a schematic diagram illustrating a playback process provided by an embodiment of the application, where after a problem occurs in the control plane of the client environment, the data saving process is performed in the client environment, and the DB module data is packaged into a compressed package by a set data export tool and sent to a developer. And after receiving the data of the DB module compressed packet, a developer imports the data of the DB module into a replay module in an experimental environment, the replay module judges whether the data comes from the DB module again, if so, imports the data into a decode module for decoding, decodes the data into a data structure which can be identified by a data plane, and finally sends the data structure to the data plane, thereby realizing a replay process based on configuration information.

After the replay flow is realized, the common debugging means such as query of control plane logs, breakpoint debugging and the like can be removed, and the control plane data query work sdn-cli is also realized. The sdn-cli tool is realized based on a gPC (graphics processing unit), a function of inquiring data information of the control plane through a cli command is realized by means of a gPC python third party packet and a control plane data cache DB (data cache database) module, and a data source is a control plane data cache module DB. The gPC is a language neutral, platform neutral, open source remote procedure call system.

Control plane key state information can be queried through the sdn-cli tool.

The CCP may query the controller for state information, including: all Tenant list information, configuration list information under a single Tenant, span (including host/topoic list) of a certain configuration or Tenant, all the topoic lists of south-to-north-to-Kafka, the topoic information of north-to-Kafka (including partition list), partition state (last offset, last op id, etc.), myid of CCP, generation id.

LCP mainly obtains virtual network device information from the local topology, including: local host, VS, VR and configuration information of related sub-resources, local single specific configuration information, local single configuration association configuration list, locally calculated fdb table of a certain DVS, locally calculated dfw rule list of a certain vm _ port; the LCP may also query the controller for status information, including: a Topic list of south Kafka, Topic information of south Kafka, a partition state (last offset, last op ID), a Redis connection status and version sync status, a DP connection status and version sync status.

The control plane may also query the system resource usage at process run time. Through the above query command, the data content, controller status, component status and system resource usage of the control plane can be obtained.

So far, based on a playback flow and an sdn-cli debugging tool, the application embodiment of the application realizes a control plane debugging mechanism based on data recording and playback.

In the application embodiment of the application, the control plane pulls the configuration information from the management plane, calculates the configuration information and sends the configuration information to the data plane, and the control plane stores the configuration information into a local database; the control plane implements a data playback function. When the control plane has errors, the control plane is pulled up again, the configuration is read from the specified database, the whole configuration calculation and issuing process is replayed, and the configuration execution process when the errors occur is accurately reproduced, so that the problems are positioned.

Therefore, the data issued to the control plane is recorded, the bug field is replayed, the replay function of the control plane is realized, and the debugging means of the control plane are enriched, so that an efficient debugging mechanism of the control plane is realized, the problem positioning difficulty of the control plane is reduced, and the problem that a complex bug is difficult to position is solved.

Based on the control plane replay module and the control plane DC module of data recording, the configuration data replay function of the control plane is realized, and the control plane can be positioned off line quickly.

In the application embodiment of the application, the control plane supports the configuration calculation and the playback of the configuration issuing process, and comprises the steps of encoding and decoding configuration data, storing the configuration data after the configuration encoding, and quickly storing the encoded configuration information into a DB module. And reading the coded configuration information from the DB module, decoding the configuration information into a data format of a data plane, and issuing the configuration information to the data plane. In addition, through debugging the replay site, after reading and decoding the configuration information from the DB, LCP enters the replay flow to reproduce the problem site, and the site debugging can be carried out by using debugging means such as log and the like.

In order to implement the method according to the embodiment of the present application, an embodiment of the present application further provides a control plane debugging apparatus, which is applied to a first node, and as shown in fig. 8, the apparatus includes:

a processing unit 801, configured to determine first configuration information from a first database;

a configuring unit 802, configured to configure a data plane network element based on the first configuration information;

an inquiring unit 803, configured to perform fault location on the first control plane after configuring the data plane network element based on the first configuration information; wherein the content of the first and second substances,

Wherein, in one embodiment, the apparatus further comprises:

a first receiving unit, configured to receive second configuration information before the processing unit 801 determines first configuration information from a first database, and write the second configuration information into the first database; and the second configuration information represents configuration information which is acquired by the second node by calling the first control plane and is issued by a management plane network element of a network where the second node is located.

In one embodiment, the first receiving unit is configured to:

and receiving the second configuration information input by a user.

In one embodiment, the first receiving unit is configured to:

and receiving the second configuration information sent by the second node.

In one embodiment, the apparatus further comprises:

a second receiving unit, configured to, before the processing unit 801 determines the first configuration information from the first database, obtain third configuration information by calling the first control plane, and write the third configuration information into the first database; the third configuration information represents configuration information issued by a management plane network element of a network where the first node is located.

In one embodiment, the network in which the first node is located further comprises a first cluster; the first cluster represents a cluster for storing configuration information issued by a management plane network element; the second receiving unit is configured to:

In one embodiment, the configuration information stored in the first database is encoded configuration information; the processing unit 801 is configured to:

In practical applications, the processing unit 801, the configuration unit 802, and the query unit 803 may be implemented by a processor in a control plane based debugging apparatus, and the first receiving unit and the second receiving unit may be implemented by a processor in a control plane based debugging apparatus in combination with a communication interface.

It should be noted that: in the control plane debugging apparatus provided in the above embodiment, only the division of each program module is exemplified when performing control plane debugging, and in practical applications, the processing distribution may be completed by different program modules according to needs, that is, the internal structure of the apparatus may be divided into different program modules to complete all or part of the processing described above. In addition, the control plane debugging device and the control plane debugging method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.

Based on the hardware implementation of the program module, and in order to implement the control plane debugging method according to the embodiment of the present application, an embodiment of the present application further provides a node. Fig. 9 is a schematic diagram of a hardware structure of a node according to an embodiment of the present application, and as shown in fig. 9, the node includes:

a communication interface 1 capable of information interaction with other devices such as network devices and the like;

and the processor 2 is connected with the communication interface 1 to realize information interaction with other equipment, and is used for executing the method provided by one or more technical schemes when running a computer program. And the computer program is stored on the memory 3.

In practice, of course, the various components in the node are coupled together by the bus system 4. It will be appreciated that the bus system 4 is used to enable connection communication between these components. The bus system 4 comprises, in addition to a data bus, a power bus, a control bus and a status signal bus. For the sake of clarity, however, the various buses are labeled as bus system 4 in fig. 6.

The memory 3 in the embodiment of the present application is used to store various types of data to support the operation of the node. Examples of such data include: any computer program for operating on a node.

It will be appreciated that the memory 3 may be either volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. Among them, the nonvolatile Memory may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a magnetic random access Memory (FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical disk, or a Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 2 described in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The method disclosed in the above embodiment of the present application may be applied to the processor 2, or implemented by the processor 2. The processor 2 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 or instructions in the form of software in the processor 2. The processor 2 described above may be a general purpose processor, a DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 2 may implement or perform the methods, steps and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the memory 3, and the processor 2 reads the program in the memory 3 and in combination with its hardware performs the steps of the aforementioned method.

When the processor 2 executes the program, the corresponding processes in the methods according to the embodiments of the present application are realized, and for brevity, are not described herein again.

In an exemplary embodiment, the present application further provides a storage medium, i.e. a computer storage medium, specifically a computer readable storage medium, for example, including a memory 3 storing a computer program, which can be executed by a processor 2 to implement the steps of the foregoing method. The computer readable storage medium may be Memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface Memory, optical disk, or CD-ROM.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, node and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic or optical disk, or various other media that can store program code.

Alternatively, the integrated units described above in the present application may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as independent products. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or portions thereof contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic or optical disk, or various other media that can store program code.

The technical means described in the embodiments of the present application may be arbitrarily combined without conflict. Unless otherwise specified and limited, the term "coupled" is to be construed broadly, e.g., as meaning electrical connections, or as meaning communications between two elements, either directly or indirectly through intervening media, as well as the specific meanings of such terms as understood by those skilled in the art.

In addition, in the examples of the present application, "first", "second", and the like are used for distinguishing similar objects, and are not necessarily used for describing a specific order or a sequential order. It should be understood that "first \ second \ third" distinct objects may be interchanged under appropriate circumstances such that the embodiments of the application described herein may be implemented in an order other than those illustrated or described herein.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the term "at least one" herein means any combination of at least two of any one or more of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Various combinations of the specific features in the embodiments described in the detailed description may be made without contradiction, for example, different embodiments may be formed by different combinations of the specific features, and in order to avoid unnecessary repetition, various possible combinations of the specific features in the present application will not be described separately.

Claims

1. A control plane debugging method is applied to a first node, and comprises the following steps:

determining first configuration information from a first database;

2. The method of claim 1, wherein prior to said determining the first configuration information from the first database, the method further comprises:

3. The method of claim 2, wherein the receiving second configuration information comprises:

and receiving the second configuration information input by a user.

4. The method of claim 2, wherein the receiving second configuration information comprises:

and receiving the second configuration information sent by the second node.

5. The method of claim 1, wherein prior to said determining the first configuration information from the first database, the method further comprises:

6. The method of claim 5, wherein the network in which the first node is located further comprises a first cluster; the first cluster represents a cluster for storing configuration information issued by a management plane network element; the obtaining of the third configuration information by invoking the first control plane includes:

7. The method according to any one of claims 1 to 6, wherein the configuration information stored in the first database is encoded configuration information; the determining the first configuration information from the first database includes:

8. A control plane debugging apparatus, comprising:

9. A node, comprising: a processor and a memory for storing a computer program capable of running on the processor,

wherein the processor is configured to execute the steps of the control plane debugging method according to any one of claims 1 to 7 when running the computer program.

10. A storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the steps of the control plane debugging method of any of claims 1 to 7.