How to Build an SDN Lab without Needing OpenFlow Hardware
How do you build a networking lab without networking equipment? Yet another plus in the column of open software driven networks. Proofing and prototyping networks today are often done with things like NETFPGA or expensive vendor manufactured hardware. Since we are beginning to build primitives, APIs and abstraction layers the value of what the software development community has had for …
Configuring an OpenFlow POX SDN Controller and HP Switches
There is an updated post with the newest HP OpenFlow firmware that can be found at: Configuring an OpenFlow POX SDN Controller and HP Switches: HP has been supporting OpenFlow v1.0 with general availability longer than anyone in the industry. While there are limitations, just as most vendors will have as we start exploring exposing and/or decoupling control planes. Installing the …
SDN Floodlight Controller GUI Topology Video and Install
SDN Floodlight Controller GUI Topology Video and Install: There is a new topology component to the OpenFlow Controller FloodLight. The page is located in the GUI Web UI under the “Topology” menu and the balls on the screen represent hosts. I haven’t checked the listserv to see where they are going with it but it’s all in the right direction …
Configuring VXLAN and GRE Tunnels on OpenvSwitch
I have done a couple of GRE tunnel how-tos using OpenvSwitch (OVS). I had been itching to give VXLan a spin in OVS so why not ferret out someones tree on GitHub. I believe VXLan is still scheduled to officially release soon in OpenvSwitch. So here are the steps for installing, configuring tunnels on OpenvSwitch with VXLan and GRE encapsulations. …
Getting Started OpenFlow OpenvSwitch Tutorial Lab : Setup
I wrote a Python OpenFlow installation app to automate an OpenFlow KVM and Open vSwitch setup found at: Getting Started OpenFlow OpenvSwitch Tutorial Lab : This is an OpenFlow Tutorial using OpenvSwitch and Floodlight controller but any other controller or switch can be used. I have had some requests on some scenarios so I put this together. Adding a few …
OpenFlow Starter Tutorial Lab #3
OpenFlow Starter Tutorial Lab #3 : Move individual flows Figure 1. OpenFlow starter tutorial Lab #3 topology. Add an entry to the wrong port and watch it break. Let’s clear all of our flows and get everything pinging the gateway again.
1 2 3 |
$curl http://192.168.1.208:8080/wm/staticflowentrypusher /clear/00:00:5c:26:0a:5a:c8:b2/json |
Add our three earlier entries from Lab1
1 2 3 |
$curl -d '{"switch": "00:00:5c:26:0a:5a:c8:b2", "name":"static-flow1", "cookie":"0", "priority":"32768", "dst-mac":"00:00:00:00:cc:10","active":"true", "actions":"output=5"}' http://192.168.1.208:8080/wm/staticflowentrypusher/json |
1 2 3 |
curl -d '{"switch": "00:00:5c:26:0a:5a:c8:b2", "name":"static-flow2", "cookie":"0", "priority":"32768", "dst-mac":"00:11:22:cc:cc:10","active":"true", "actions":"output=6"}' http://192.168.1.208:8080/wm/staticflowentrypusher/json |
1 2 3 |
$curl -d '{"switch": "00:00:5c:26:0a:5a:c8:b2", "name":"static-flow3", "cookie":"0", "priority":"32768", "dst-mac":"22:22:22:00:cc:10","active":"true", "actions":"output=7"}' http://192.168.1.208:8080/wm/staticflowentrypusher/json |
Start tcpdump on the host you will send …
OpenFlow Starter Tutorial Lab #2
OpenFlow Starter Tutorial Lab #2 :This lab is to restrict two hosts to only talk to each other with source based forwarding using the static flow pusher RESTful API. You can add any field you want to make the forwarding decisions on. Remember to name the flows with unique names or else you will overwrite previously instantiated flows. Previous posts …
OpenFlow Starter Tutorial Lab #1
Figure 1. The topology for the lab simulates in software the same capabilities you can get in hardware thanks to OpenvSwitch.[/crayon] This setup allows you to add and remove as many matches into the API calls and tinker with them to get a feel once you nail down the basics. Then you can write the next “killer app” get rich …