60 likes | 255 Views
Testing an Openflow switch. 1 TestCenter port will be used as Openflow controller 2 (or more) TestCenter ports will be used to generated and analyze traffic. Setting up the configuration. OpenvSwitch1 Configuration IPv4 = 192.85.1.1 ( ethernet nic eth4) DPID = C29AE3B3E
E N D
Testing an Openflow switch • 1 TestCenter port will be used as Openflow controller • 2 (or more) TestCenter ports will be used to generated and analyze traffic
Setting up the configuration • OpenvSwitch1 Configuration • IPv4 = 192.85.1.1 (ethernetnic eth4) • DPID = C29AE3B3E • Controller = tcp:192.85.1.3:6633 • Port 1 (ethernetnic eth0) connected to 10.14.16.154//1/1 • Port 2 (ethernetnic eth1) connected to 10.14.16.155//1/1
Defining Flows & Traffic • Emulation supports 2 methods of defining Openflow flows • Bound to traffic – flows defined by OpenFlow switch port configuration, flow parameters, & traffic field values • Flow table text - flows defined by lines of text in same format as Openvswtichovs-ofctl or reference controller dpctl command line utilities
Adding more switches… • TestCenter supports multiple Openflow switch configurations too
Adding More Switches (Openvswitch2) • OpenvSwitch2 Configuration • IPv4 = 192.85.1.11 (ethernetnic eth2) • DPID = C291C8FD8 • Controller = tcp:192.85.1.3:6633 • Port 1 (ethernetnic eth0) connected to vswitch-1 Port 3 • Port 2 (ethernetnic eth1) connected to vswitch-3 Port 1
Adding More Switches (Openvswitch3) • OpenvSwitch3 Configuration • IPv4 = 192.85.1.12 (ethernetnic eth1) • DPID = C2976CBE8 • Controller = tcp:192.85.1.3:6633 • Port 1 (ethernetnic eth0) connected to vswitch-2 Port 2 • Port 2 (ethernetnic eth1) connected to 10.14.16.156//1/1