1. Introduction

This document describes the setup and operation of OpenFlow network.

2. OpenFlow Datapath Network Design

2.1 IP address Space Allocation

Although OpenFlow does not limit the address to IP, we would expect most of the user/experimenter use IP address space for backward compatibility of endsystem. You can allocate entire IP subnet space for OpenFlow or choose to use a subset of the currently used IP address space for OpenFlow.

2.1.1. Allocating Entire IP Address Space

In this case, OpenFlow island is isolated to dedicated broadcast domain which simplifies the operation in several ways.

• Pros
• • Broadcast storm incident in OpenFlow network (which may be created by the experimenter) won't affect to other network
  • Make debugging easy because you don't see broadcast/multicast traffic from non-OpenFlow network
• Cons
• • Need to change IP address for users to opt-in OpenFlow network. If users use DHCP and there is no network access policy tied to IP address, then it won't be a problem.
  • Need additional address space.

2.1.2. Using a part of the existing IP subnet space

• Pros
  • Easy for opt-in for the user. Users can choose OpenFlow or non-OpenFlow network without changing their IP address.
• Cons
  • There is no broadcast boundary between OpenFlow and non-OpenFlow network, which may make debugging difficult and make non-OpenFlow network vulnerable for the accident in OpenFlow network.

2.2. DHCP Service

How to provide DHCP service for the OpenFlow network user coexisting with the campus wide DHCP infrastructure.

2.3. Redundancy

How to run spanning tree in OpenFlow network.

3. Controller Network Design

Difference between L2-inband and L3-inband.

4. OpenFlow Controller

List of the available controllers. Give the overview of each controller and explain the difference.

4.1. OpenFlow Reference Controller

4.2. NOX

4.3. Beacon ( home page)

5. Slicing OpenFlow Network

5.1. Slicing via VLAN

5.2. Slicing via FlowVisor

6. Operating OpenFlow Network

7. OpenFlow Network Monitoring

Packetloss, delay, delay jitter are very well known performance measure in the network. In OpenFlow network, there are additional metrics the operator should care/monitor to keep OpenFlow network healthy.

7.1. Switch CPU Usage

7.2. Flow Setup Time

7.3. Flow Entry Usage

Appendix: Stanford Network Configuration/Operation Example