Method and device for transmitting upper-supply controller protocol message in SDN network

Abstract

The invention discloses a method and device for transmitting an upper-supply controller protocol message in an SDN network. The method comprises the steps: receiving a flow and enabling the flow to be matched with a flow table item, wherein the flow table item comprises a control flow table item; enabling the flow to be packaged in the upper-supply controller protocol message and to be transmitted to a controller and generating the control flow table item matched with the flow when there is no flow table item matched with the flow and the flow is of a preset message type, wherein the operation of the control flow table item is forbidding the transmission of the flow to the controller; and forbidding the transmission of the flow to the controller according to the matched control flow table item when the flow table item matched with the flow is the control flow table item. According to the embodiment of the invention, the effectiveness of the upper-supply controller protocol message is improved, and the failures, caused by a large amount of ineffective upper-supply controller protocol messages, of flow transmission are reduced.

Description

technical field [0001] The invention relates to the field of communication technologies, in particular to a method and a device for sending and sending controller protocol messages in an SDN network. Background technique [0002] Software Defined Network (Software Defined Network, SDN) is a new type of network architecture. Its core idea is to separate the control plane and forwarding plane of network equipment, and to centralize and flexibly control network traffic through the controller, so as to provide core network and application Innovation provides a good platform. [0003] In an OpenFlow-based SDN network, all hosts are connected to an openflow switch and connected to the SDN network through the openflow switch. Among them, when the host sends traffic, it first sends the traffic to the controller through the openflow switch through the protocol packet, such as a packet-in packet, and sends it to the controller, and then the controller sends the dynamic flow table to ...

AI Technical Summary

Problems solved by technology

[0007] It can be seen that in the OpenFlow-based and overlay-based SDN network, on the openflow switch or OVS node, when there are many PCs or VMs connected below it, there will be more packet-in messages that need to be sent to the controller. When the controller processes the packet-in message, the delay will be relatively long, resulting in that the PC or VM cannot obtain the ARP address in time, and the openflow switch or OVS cannot obtain the forwarding flow table in time. At this time, the PC will resend the message to apply for the ARP address , the openflow switch or OVS will continue to encapsulate the data flow message that has not obtained the flow table into a packet-in message and send it to the controller, which forms a lot of repeated packet-in messages to the controller, and the control The controller needs to process each packet-in message, which will intensify the pressure on the controller to process the message

When these packet-in packets reach the maximum capacity of the openflow switch or OVS to send packet-in packets, many valid packet-in packets will be discarded, resulting in PCs or VMs not getting ARP The address, openflow switch or OVS cannot get the forwarded flow table, which leads to the failure of user traffic to respond and the traffic to fail.

[0008] The above-mentioned flow blocking situation has occurred many times in actual networking, and once it happens, the protocol packets sent to the controller, such as packet-in packets, which are subsequently lost by openflow switches or OVS switching nodes, will be regenerated, resulting in More and more protocol packets are sent to the controller, and the controller also needs to repeatedly process many of the same protocol packets sent to the controller, which eventually leads to the complete forwarding failure of the entire openflow switch or switching nodes such as OVS

Images