Nov 11, 2016

OpenSource Controller

Software Defined Network (SDN) becomes more and more popular. Controller becomes more and more important. A lot of controllers have been developed. NOX, Ryu and Floodlight are classic.

NOX 

NOX was initially developed at Nicira Networks side-by-side with OpenFLow - NOX was the first OpenFlow controller. NOX at its core only provides very low-level methods for interfacing with networks. NOX is based on C++ on Linux


ROX

Young sibling of NOX. Primary target is research. Python-based.


Open Daylight

Linux foundation group, Hydrogen, is the frist simulataneous release of OpenDaylight delivering three different editions to help a wide array of users get up and running as quickly as possible - Base Edition, Virtualization, Edition, and Service Provider Edition


Floodlight

Enterprise-class, Apached-licensed, Java-based OpenFlow controller, the alternative to Open Daylight for commerical vendors base code.


RYU

Ryu is a component-based software-dfined networking framework based on Python.


Trema

Trema is full-stack, easy-to-use framework for developing OpenFlow controllers in Ruby and C


Beacon

Beacon is fast, cross-platform, modular, Java-based OpenFlow controller that supports both Event-based and threaded operation.


ovs-controller

Trivial reference controller packaged with Open vSwitch.

Nov 7, 2016

ExtremeWireless - BYOD Lab - 5

Wireless Topology Design. 

In this lab, we create tow typologies: VLAN200AP and VLAN200AC.

At VLAN200AP, the traffic will be tagged by the Access Point before entering the network.


















At VLAN200AC, the traffic will be tunneled to the Controller.





















We could use the following CLI commands by "show topology"
EWC1.wirelessdeom.com# show topology

Name                    Mode      L2:VlanId,tagged,port  L3:IP,GW,DHCP            L3:IPv6,Auto-Generated

Admin                   admin     N/A,N/A,Admin          192.168.1.1,none,N/A     N/A,
Bridged at AP untagged  b@ap      4093,disable,N/A
Physical1               physical  100,disable,esa0       192.168.10.4,none,none
VLAN200AC               b@ac      200,enable,esa0        192.168.20.4,none,relay
VLAN200AP               b@ap      200,enable,N/A


Role Design

We also create two roles - Student and Staff, in this lab.
































We could use the following CLI commands by "show role"
EWC1.wirelessdeom.com# show role

Role name        Topology   Class of Service  Mode       Filter defined

Enterprise User  no-change  no-change         no-change  Yes
Student          no-change  no-change         no-change  Yes
Staff            no-change  no-change         no-change  Yes
Printer          VLAN200AC  no-change         b@ac       Yes
Unregistered     VLAN200AC  no-change         b@ac       Yes
Guest            VLAN200AC  no-change         b@ac       Yes
Extreme          VLAN200AC  no-change         b@ac       Yes