CN112737933B

CN112737933B - Gateway system based on cloud scene and gateway communication method

Info

Publication number: CN112737933B
Application number: CN202011573194.6A
Authority: CN
Inventors: 赵海平
Original assignee: Inspur Cisco Networking Technology Co Ltd
Current assignee: Inspur Cisco Networking Technology Co Ltd
Priority date: 2020-12-24
Filing date: 2020-12-24
Publication date: 2022-12-23
Anticipated expiration: 2040-12-24
Also published as: CN112737933A

Abstract

The application discloses a gateway system and a gateway communication method based on a cloud scene, which are used for solving the problems that the existing communication between nodes lacks an effective control plane protocol and the reachability between the nodes needs to be configured manually. The system comprises an SDN controller, a network controller and a network controller, wherein the SDN controller is used for managing a plurality of nodes; the FRR protocol stack is arranged in each node and used for issuing the network segment address of the node to other nodes, receiving the network segment addresses of other nodes and generating routing list items from the node to other nodes according to the network segment addresses of other nodes and the node; and the vector data packet processing framework VPP runs in each node and is used for matching a forwarding table entry from the routing table entry according to the forwarding request of the node so as to enable the node to send the data packet to other nodes based on the forwarding table entry. By combining the SDN with the FRR protocol stack and the VPP, unified management of the nodes is realized, and by means of an effective routing protocol, reachability among the nodes and efficient forwarding of data can be realized without manual configuration work.

Description

Gateway system based on cloud scene and gateway communication method

Technical Field

The application relates to the technical field of gateways, in particular to a gateway system and a gateway communication method based on a cloud scene.

Background

With the development of cloud computing and virtualization and the coming of the internet era, the number of various network services is increasing explosively. Based on the requirements of the user network, the network elements are required to be flexibly deployed so as to realize the flexible expansion of the network elements. Therefore, cloud computing requires a cloud data center to support high-performance forwarding, support large-scale networking, communicate with a traditional network through a routing protocol, and dynamically respond to changes of the network.

At present, the mainstream mode is to realize interconnection of virtual networks of users through an OpenStack cloud platform. However, in the case of large-scale networking, the communication between nodes lacks an efficient control plane protocol, and the inter-node reachability needs to be configured manually. With the expansion of the tenant scale and the increase of the number of virtual machines, a large amount of manual configuration work is required, and great challenges are brought to the management difficulty, the forwarding performance and the system stability.

Disclosure of Invention

The embodiment of the application provides a gateway system and a gateway communication method based on a cloud scene, and is used for solving the problems that under the condition of large-scale networking, communication between nodes lacks an effective control plane protocol, reachability between nodes needs to be manually configured, and huge challenges are brought to management difficulty, forwarding performance and system stability

An embodiment of the present application provides a gateway system based on a cloud scenario, including:

an SDN controller for managing a plurality of nodes; the FRR protocol stack is arranged in each node and used for issuing the network segment address of the node to other nodes, receiving the network segment addresses of other nodes and generating a routing list item from the node to other nodes according to the network segment addresses of other nodes and the node; and the vector data packet processing framework VPP runs in each node and is used for matching a forwarding table entry from the routing table entry according to the forwarding request of the node so as to enable the node to send a data packet to other nodes based on the forwarding table entry.

In one example, the FRR protocol stack is configured to monitor a routing change in a system, and automatically modify a routing table entry corresponding to a node according to the monitored routing change; the route change comprises adding nodes and deleting nodes.

In one example, an SDN controller is configured to send first configuration information to the VPP in each node, and configure basic information of the VPP; and the system is further configured to send second configuration information to the FRR protocol stack in each node, and configure a protocol running in the FRR protocol stack.

In one example, the system further comprises: and the monitoring module is used for monitoring the routing table entry and notifying the VPP when the routing table entry is monitored to be changed.

In an example, the FRR protocol stack is further configured to create a tunnel for data forwarding according to EVPN protocol configuration information issued by the SDN controller, so that the node forwards a data packet through the tunnel.

In one example, the FRR protocol stack is further configured to obtain a network segment address of an external network, and generate a routing table entry from the cost node to the external network according to the network segment addresses of the external network and the local node.

In one example, the VPP is further configured to match a forwarding entry from the routing entry based on a forwarding request of the node to the external network, so that the node sends a data packet to the external network based on the forwarding entry.

In one example, the FRR protocol stack is further configured to run a plurality of routing protocols, interact with routing protocols of FRR protocol stacks of other nodes, and generate a routing table entry; the routing protocol comprises a BGP protocol, an OSPF protocol and an EVPN protocol.

In one example, the routing table entry includes a destination address, a network mask, a routing priority, a routing overhead, a next hop IP address, an output interface.

The gateway communication method based on the cloud scene provided by the embodiment of the application comprises the following steps:

the network segment address of the node is issued to other nodes in the system through an FRR protocol stack, and the network segment addresses of other nodes are received; generating a routing table item from the node to other nodes according to other nodes and the network segment address of the node; and matching a forwarding table entry from the routing table entry according to the forwarding request of the node through the VPP, and sending a data packet to other nodes based on the forwarding table entry.

The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects:

by combining the SDN with the FRR protocol stack and the VPP, unified management of the nodes is realized, and by means of an effective routing protocol, reachability among the nodes and efficient forwarding of data can be realized without manual configuration work, so that a large-scale high-performance pure software gateway system is provided.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a structural diagram of a gateway system based on a cloud scenario according to an embodiment of the present application;

fig. 2 is a schematic diagram of communication between an FRR protocol stack and a VPP according to an embodiment of the present application;

fig. 3 is a flowchart of a gateway communication method based on a cloud scenario according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. 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 application.

At present, the mainstream mode is to realize interconnection of virtual networks of users through an OpenStack cloud platform. However, in the case of large-scale networking, the communication between nodes lacks an efficient control plane protocol, and the inter-node reachability needs to be configured manually. With the expansion of tenant size and the increase of the number of virtual machines, a large amount of manual configuration work is required, and great challenges are brought to the management difficulty, the forwarding performance and the system stability.

According to the embodiment of the application, the SDN is combined with the FRR protocol stack and the VPP, unified management of the nodes is achieved, reachability among the nodes and efficient forwarding of data can be achieved without manual configuration work through an effective routing protocol, and a large-scale high-performance pure software gateway system is provided.

Fig. 1 is a structural diagram of a gateway system based on a cloud scenario, which includes an SDN controller 100, an frr protocol stack 110, and a Vector Packet Processing framework (VPP) 120.

In this embodiment of the present application, the SDN controller 100 is configured to perform unified management on multiple nodes, so that data forwarding is performed between the multiple nodes; the FRR protocol stack 110 is disposed in each node, and when the node is added to the constructed gateway system, it issues the network segment address of the node to other nodes, and receives the network segment addresses of other nodes, so as to generate a routing table from the node to other nodes according to the network segment addresses of other nodes and the node; the vector data packet processing framework VPP120 operates in each node, and when the node needs to forward a data packet to another node, the VPP120 matches a corresponding forwarding table from a pre-generated routing table according to a forwarding request of the node, so that the node sends the data packet to another node based on the matched forwarding table.

Among them, software Defined Network (SDN) is a new Network innovation architecture, and is an implementation manner of Network virtualization. The core technology OpenFlow separates the control plane and the data plane of the network equipment, thereby realizing the flexible control of network flow, enabling the network to be more intelligent as a pipeline, and providing a good platform for the innovation of a core network and application.

The node comprises a plurality of different types of equipment and a plurality of equipment of different communication systems, and specifically comprises equipment such as a switch and a router.

FRrouting (FRR) is a suite of IP routing protocols for Linux and Unix platforms, the seamless integration of FRR with native Linux/Unix IP networking stacks making it suitable for use in a wide variety of use cases, including connecting hosts/virtual machines/containers to the network, advertising web services, LAN switching and routing, internet access routers, and Internet peering.

The Vector Packet Processor (VPP) framework is an extensible framework that provides out-of-box switch/router functionality.

According to the embodiment of the application, the SDN is combined with the FRR protocol stack and the VPP, so that real cloud network linkage is realized, a large-scale high-performance pure software network scheme is realized, and flexible networking is supported. The FRR and the VPP are interacted to realize the automatic synchronization of the VPP forwarding table item and the routing protocol, flexibly respond to the network change and improve the data forwarding efficiency of the system.

In this embodiment of the present application, the FRR protocol stack 110 is configured to monitor a route change generated in a system, and automatically modify a routing table entry corresponding to the node according to the monitored route change; the route change comprises the addition of nodes, the deletion of nodes and the change of node addresses.

Specifically, when a node is newly added to the system, the FRR protocol stack 120 is configured to obtain a network segment address issued by the newly added node, and generate a routing table entry from the node to the newly added node; when deleting a node in the system, the FRR protocol stack 120 deletes a routing table entry between the node and the deleted node according to the network segment address of the deleted node; when the routing table entry of the node in the system fails, a backup routing table entry is provided for the node.

Wherein the routing table entries represent paths between nodes. The content of the routing table entry comprises a destination address, a network mask, a routing priority, a routing overhead, a next hop IP address and an output interface. The destination address is used for identifying the destination address of the data packet or a destination network; the network mask identifies the network segment address of the destination node together with the destination address; route priority, which identifies the priority of the route joining the IP routing table. When a destination is reached, a plurality of routes are provided, and the nodes can select the route with high priority for preferential utilization according to the priority of the route; when the priority of a plurality of routes reaching a destination is the same, the route with the minimum route cost becomes the optimal route; an output interface indicating from which interface the data packet is to be forwarded from the node; the next hop IP address indicates the next router through which the packet passes.

According to the embodiment of the application, the routing table items are adaptively modified through the FRR protocol stack according to the routing change in the system, so that the routing table items and the routing change are automatically synchronized, the routing table items can flexibly respond to the network change, the routing table items among nodes do not need to be manually configured, the manual workload is reduced, and the data forwarding efficiency is greatly improved.

And after the routing table entry changes, when the VPP is matched with the forwarding table entry, the matched forwarding table entry can be automatically synchronized according to the change of the routing table entry, and meanwhile, the forwarding table entry responds to the change of the network, so that the efficiency of data forwarding between nodes can be greatly improved.

In this embodiment of the application, the SDN controller 100 is configured to send first configuration information to the VPP120 in each node, configure basic information of the VPP120, and enable the VPP120 to interact with the VPP120 in another node according to a rule of the first configuration information; and is further configured to send second configuration information to the FRR protocol stack 110 in each node, and configure each protocol running in the FRR protocol stack 110.

Specifically, the system comprises an Agent130 running on a node, wherein the Agent is used as a proxy of the node and is managed by the SDN controller. The Agent130 receives first configuration information sent by the SDN controller 100, and issues the first configuration information to the VPP120, and is further configured to receive second configuration information sent by the SDN controller 100, and issues the second configuration information to the FRR protocol stack 110.

In the embodiment of the application, the SDN controller realizes management of basic configuration of routing protocols of the FRRs on the nodes through the Agent, and the routing on each node is uniformly controlled and issued with the basic configuration according to global planning of the SDN controller, so that centralized management of a cloud network is realized, and an efficient and flexible gateway system is provided.

In this embodiment of the present application, the system further includes a monitoring module (not shown in the figure) configured to monitor the routing table entry, and notify the VPP120 when it detects that the routing table entry changes, so that the VPP120 matches the forwarding table entry from the updated routing table entry.

In this embodiment of the application, since the FRR protocol stack 110 supports the EVPN protocol, the FRR protocol stack is further configured to receive EVPN protocol configuration information issued by the SDN controller, and create a tunnel for data forwarding according to the EVPN protocol configuration information issued by the SDN controller, so that the node forwards a data packet to another node through the tunnel, which may meet a large-scale networking condition.

In this embodiment, the FRR protocol stack 110 is further configured to obtain a network segment address of an external network, and generate a routing table entry from the cost node to the external network according to the external network and the network segment address of the node, so that the node forwards a data packet to the external network.

In this embodiment, the VPP120 is further configured to match a forwarding entry from the routing entry based on a forwarding request of the node to the external network, so that the node sends a data packet to the external network based on the forwarding entry.

According to the embodiment of the application, the FRR protocol stack is configured through the SDN controller, the intercommunication of the gateway node and the dynamic routing protocol of the traditional external network is realized, the manual workload is reduced, and the efficiency of the system can be greatly improved.

Fig. 2 is a schematic diagram of communication between an FRR protocol stack and a VPP provided in an embodiment of the present application, and as shown in fig. 2, a plurality of routing protocols run on an FRR protocol stack 110, and a node interacts with routing protocols of FRR protocol stacks 110 of other nodes through the routing protocols to generate a routing table entry; when the node generates a forwarding request, the VPP120 communicates with the FRR protocol stack 110, matches a corresponding forwarding entry from the routing entry, and forwards the packet of the node to the VPP of the destination node through the forwarding entry. The routing protocol comprises a BGP protocol, an OSPF protocol and an EVPN protocol.

In the embodiment of the application, as the VPP supports rich data plane characteristics, security services such as Firewall and VPN can be uniformly managed through the SDN.

In the embodiment of the application, for virtual machine communication on the Overlay layer, the FRR supports automatic publishing of the Overlay host route, and can meet the flexible virtual machine migration requirement.

The general framework of the virtualization technology mode is to implement the bearer applied to the network without modifying the basic network in a large scale, and can be separated from other network services, and is based on the IP-based basic network technology.

Based on the same inventive concept, the cloud-scene-based gateway system structure diagram provided in the embodiment of the present application further provides a corresponding cloud-scene-based gateway communication method flowchart, as shown in fig. 3.

Fig. 3 is a flowchart of a gateway communication method based on a cloud scenario provided in an embodiment of the present application, which specifically includes the following steps:

s101: and issuing the network segment address of the node to other nodes in the system through an FRR protocol stack, and receiving the network segment addresses of other nodes.

S102: and generating routing list items from the node to other nodes according to other nodes and the network segment address of the node.

S103: and matching a forwarding table entry from the routing table entry according to the forwarding request of the node through the VPP, and sending a data packet to other nodes based on the forwarding table entry.

It should be noted that the gateway communication method based on the cloud scenario and the gateway system based on the cloud scenario provided in the embodiment of the present application are based on the same principle, and the specific process is described in detail in the system embodiment, which is not described herein again.

The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the method embodiment, since it is substantially similar to the system embodiment, the description is simple, and the relevant points can be referred to the partial description of the system embodiment.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.

The description has been presented with reference to flowchart illustrations and/or block diagrams of systems, methods, and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

All the embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the apparatus, device, and non-volatile computer storage medium embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference may be made to the partial description of the method embodiments for relevant points.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The above description is merely one or more embodiments of the present disclosure and is not intended to limit the present disclosure. Various modifications and alterations to one or more embodiments of the present description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of one or more embodiments of the present specification should be included in the scope of the claims of the present specification.

Claims

1. A gateway system based on a cloud scenario, comprising:

an SDN controller for managing a plurality of nodes;

the FRR protocol stack is arranged in each node and used for issuing the network segment address of the node to other nodes, receiving the network segment addresses of other nodes and generating a routing list item from the node to other nodes according to the network segment addresses of other nodes and the node;

the vector data packet processing framework VPP runs in each node and is used for matching a forwarding table entry from the routing table entry according to a forwarding request of the node so that the node sends a data packet to other nodes based on the forwarding table entry;

the SDN controller is further configured to send first configuration information to the VPPs in the nodes, and configure basic information of the VPPs; and the system is further configured to send second configuration information to the FRR protocol stack in each node, and configure a protocol running in the FRR protocol stack.

2. The system of claim 1, wherein the FRR protocol stack is configured to monitor a routing change in the system and automatically modify a routing table entry corresponding to the node according to the monitored routing change; the route change comprises adding nodes and deleting nodes.

3. The system of claim 1, further comprising:

and the monitoring module is used for monitoring the routing table entry and informing the VPP when the routing table entry is monitored to be changed.

4. The system of claim 1, wherein the FRR protocol stack is further configured to create a tunnel for data forwarding according to EVPN protocol configuration information issued by the SDN controller, so that the node forwards a data packet through the tunnel.

5. The system of claim 1, wherein the FRR protocol stack is further configured to obtain a network segment address of an external network, and generate a routing table entry from the cost node to the external network according to the network segment addresses of the external network and the local node.

6. The system of claim 5, wherein the VPP is further configured to match a forwarding entry from the routing entry based on a forwarding request of the node to the external network, so that the node sends a packet to the external network based on the forwarding entry.

7. The system of claim 1, wherein the FRR protocol stack is further configured to run a plurality of routing protocols to interact with routing protocols of FRR protocol stacks of other nodes to generate routing table entries; the routing protocol comprises a BGP protocol, an OSPF protocol and an EVPN protocol.

8. The system of claim 1, wherein the routing table entry comprises a destination address, a netmask, a routing priority, a routing overhead, a next hop IP address, and an output interface.

9. A gateway communication method based on a cloud scenario is applied to the system of any one of claims 1 to 8, and is characterized in that the method comprises the following steps:

the network segment address of the node is issued to other nodes in the system through an FRR protocol stack, and the network segment addresses of other nodes are received;

generating a routing table item from the node to other nodes according to other nodes and the network segment address of the node;

matching forwarding table entries from the routing table entries according to the forwarding request of the node through the VPP, and sending data packets to other nodes based on the forwarding table entries;

sending first configuration information to the VPP in each node through an SDN controller, configuring basic information of the VPP, sending second configuration information to the FRR protocol stack in each node, and configuring a protocol running in the FRR protocol stack.