SDN Controller Test Feature V: Floodlight performance test report (top)

The previous article focused on the SDN Controller Test topic four : Floodlight test Report for South-to-North interface ( bottom ) , the function test results of the controller are given. This article will test the floodlight controller According to the determined performance test item, and give the test result.

1 Purpose of testing

Verify The following performance scenarios for the Floodlight v1.0 controller:

Verify the maximum size of the controller support switch on-line;

Verify that the controller supports the optimal number of switches on-line;

Verify the speed of the Controller flow table;

Verify that the Controller flow table is issued with a delay;

The maximum number of flow tables supported by the validation control;

Verify The learning speed of the controller MAC address;

Verify the network topology update speed of the controller in the case of large-scale switch on-line;

2 the need for performance testing

The controller is responsible for the centralized control of the entire SDN Network, and has the important role of controlling the whole network view and improving the whole network resources. But because of the centralization of the control ability, it means that the controller can easily become the bottleneck of the future whole network performance. In order to prevent the prevention, the controller performance test, a comprehensive understanding of the performance of the controller products, provide reliable performance indicators, it is particularly important.

3 Performance Bottleneck analysis

The SDN controller has centralized control and dispatch of the equipment in the whole network through the south-to-network controller technology. Includes link discovery, topology management, policy development, and table entry.

Workflow for 3.1 SDN Controller

the workflow for the SDN controller is as follows:

650) this.width=650; "title=" 111.jpg "src=" http://s3.51cto.com/wyfs02/M01/5A/1E/ Wkiom1t2t0vrcos5aaeimnwoac4336.jpg "alt=" Wkiom1t2t0vrcos5aaeimnwoac4336.jpg "/>

1) The controller and the switch establish the ofchannel Channel, the controller controls and manages the switch through the Ofchannel.

2) When the switch receives a packet and there are no matching entries in the stream table, the Exchange opportunity encapsulates the packet in the packet_in message to the controller, at which time the packet is cached in the switch waiting to be processed.

3) Controller receivedpacket_inmessage, you can sendFlow_modmessage writes a stream table entry to the switch andFlow_modin the messagebuffer_idfield is set topacket_inin the messagebuffer_idvalues. Thus the controller writes a packet-related stream table entry to the switch and specifies that the packet follows the flow table entryActionlist processing. However, not all packets need to add a flow table entry to the switch to match processing, and there are a number of packets in the network that appear in very small quantities (such asArp,igmpetc.), so that there is no need to specify the processing of this class of packets through a flow table entry, where the controller can usePacket_outmessage that tells the switch how a packet is handled.

3.2 Performance Bottleneck analysis

sdn Span style= "font-family: ' The song Body '; > The workflow of the network, it is known that the controller responds to packet_in message send packet_out/flow_mod The speed of the message is very important, it directly affects the controller topology discovery, Flow table issued, mac address learning ability, and even the performance of the entire network. and sdn The network typically uses a reactive-flow installation, The response time of the controller directly affects the processing speed of the flow installation, this article will focus on testing the controller handling the packet_in message throughput and response time. Also focus on the controller support for creating openflow the ability to connect and the speed of the topology update.

4 test Environment hardware configuration

650) this.width=650; "title=" 222.jpg "src=" http://s3.51cto.com/wyfs02/M02/5A/1E/ Wkiom1t2t3mip2siaahyqugeqbg697.jpg "alt=" Wkiom1t2t3mip2siaahyqugeqbg697.jpg "/>

5 Test Execution

5.1 Verifying the maximum size of the controller support switch on-line

5.1.1 Test Purpose

Verify the maximum number of switches that the controller can access.

5.1.2 Test Topology

650) this.width=650; "style=" Float:none; "title=" 333.jpg "src=" http://s3.51cto.com/wyfs02/M00/5A/1A/ Wkiol1t2ulvabuz5aaes7lcvgre856.jpg "alt=" Wkiol1t2ulvabuz5aaes7lcvgre856.jpg "/>

650) this.width=650; "style=" Float:none; "title=" 444.jpg "src=" http://s3.51cto.com/wyfs02/M00/5A/1E/ Wkiom1t2t6fhy4cmaanc9mydoye532.jpg "alt=" Wkiom1t2t6fhy4cmaanc9mydoye532.jpg "/>

650) this.width=650; "style=" Float:none; "title=" 555.jpg "src=" http://s3.51cto.com/wyfs02/M01/5A/1A/ Wkiol1t2ulyq9asyaaww6xxlsz0031.jpg "alt=" Wkiol1t2ulyq9asyaaww6xxlsz0031.jpg "/>

650) this.width=650; "style=" Float:none; "title=" 666.jpg "src=" http://s3.51cto.com/wyfs02/M01/5A/1E/ Wkiom1t2t6mcpfjwaawd4sxce0m853.jpg "alt=" Wkiom1t2t6mcpfjwaawd4sxce0m853.jpg "/>

650) this.width=650; "style=" Float:none; "title=" 777.jpg "src=" http://s3.51cto.com/wyfs02/M02/5A/1A/ Wkiol1t2ul2xaj0vaakinaw8eyw310.jpg "alt=" Wkiol1t2ul2xaj0vaakinaw8eyw310.jpg "/>

This test project is not finished, the following test results can point this View Original .

SDN Controller Test Feature V: Floodlight performance test report (top)