Scribd
Upload
7 views3 pages

SDN2

Uploaded by

Rohit Moon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views3 pages

SDN2

Uploaded by

Rohit Moon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

SDN 2

Start the POX controller


Before we start the POX SDN controller, we need to determine which components we
want to run when we start the controller.

Select the POX components to run


To select the correct stock components, determine what behavior we want the network
of switches to exhibit. Then we will select the stock POX component that provides that
functionality.

In this practical, we will use components that make POX work like a Layer 2 learning
switch, and that dump copies of packets received by the controller to thecontroller’s log
file (so we can see what packets the controller sees), and that listcontroller events to the
console log screen in an easy-to-read format. According to the POX documentation,
the stock components that do these tasks are: forwarding.l2_pairs, info.packet_dump,
samples.pretty_log, and log.level.

Start POX

To start the POX controller with the selected stock components, enter thefollowing
command on a terminal session connected to the Mininet VM.

mininet-vm:~$ sudo ~/pox/pox.py forwarding.l2_pairs \ info.packet_dump

samples.pretty_log log.level --DEBUG


In the POX console, see that the log shows the controller starts and connects tothe
switches previously set up by the Mininet network simulator:
Test the controller
The forwarding.l2_pairs component is a very simple application that just
matchesMAC addresses so it creates a simple scenario to study.

Generate some test traffic between hosts to see how POX builds flows in the
network. Run the p command, which runs ping tests between each
Mininet i
n
g
a
l
l
host in the emulated network. This generates traffic to the controller every
time aa switch receives a packet that has a destination MAC address that is
not alreadyin its flow table.

You can see in the POX console window the log messages showing what is
happening. When the POX controller running the forwarding.l2_pairs
componentreceives a packet from a switch, it tells the switch to flood the ARP
packet out itsother ports to other switches or hosts. One host eventually
responds to the ARP request and then the forwarding.l2_pairs component
sends OpenFlow messages to each switch to load the required flows into the
switch flow tables.
Checking flow tables
To see the contents of the flow tables on all switches, execute the Mininetcommand:

mininet> dpctl dump-flows

To check ARP tables on each host, execute the Mininet arp command.
Forexample, to show the ARP table for host h1, enter the following
command:

mininet> h1 arp

To clear all flow tables on all switches, enter the Mininet command:

mininet> dpctl del-flows

You might also like