1

SDN Dev Group, Week 2

Aaron Gember Aditya AkellaUniversity of Wisconsin-Madison

Wisconsin Testbed; Design Considerations

2

Development Progress

• High-level design• Problems encountered• Lessons learned• Experience with specific controllers

3

Wisconsin

Testbed

4

Testbed Components

• Switches– 3x HP ProCurve 5400– 4x HP ProCurve 6600

• Servers– 15x Dell PowerEdge R210 (Quad-core Intel Xeon

X3430, 4GB RAM, 2x 1Gbps)– 5x Dell Precision T5500 (Dual quad-core Intel Xeon

E5507, 12GB RAM, 1x 1Gbps)– 5x HP dc5800 (Core 2 Duo, 2GB RAM, 2x 1Gbps)

5

Testbed TopologyCS 4th Floor East

4300EProCurve 6600

CS 4th Floor West4300F

ProCurve 6600

CS 6th Floor West6300E

ProCurve 5400

CS 6th Floor West6300F

ProCurve 5400CS 3360 (WINGS)

WINGSProCurve 5400CS 3390 (WAIL)

WAILProCurve 6600

CS 3390 (WAIL)WAILTWO

ProCurve 6600

CS Network

Internet

6

• Federation of network testbeds: OpenFlow (campuses, NLR, I2), Emulab, PlanetLab, etc.

• Live resource map: http://protogeni.net/flack• GENI software stack: FlowVisor, FOAM• Experimenters create a slice + slivers at each

site to reserve the resources they want

7

Testbed for SDN Dev Group

CS 3360 (WINGS)WINGS

ProCurve 5400

1

2

3

eth1.2** eth1.2** eth1.2**

thrush lyrebird vulture

wings-openflow-1

Controller

8

Accessing the testbed

• SSH to wings-openflow-1.wail.wisc.edu(from anywhere on the Internet)Username: CS username; Password: w3lcom3

• Reset your password by running passwd• Home directory is shared using NFS

Local storage on each machine at /scratch• SSH to vulture, thrush, and lyrebird to run

commands on these end-hosts

9

“Slices” for SDN Dev Group

• Should reserve resources in FOAM/FlowVisor using GENI Rspecs

• Statically allocated VLANs (201 – 210)• Controller should run on wings-openflow-1

and listen on port 102**• Generate traffic on vulture, lyrebird, and

thrush on interface eth1.2** using IP addresses 10.2.**.0/32

10

Design Considerations

• Granularity of flow entries• Static vs. dynamic flow installation• Switch flow table size limits• Policy input• Code re-use/modular design

11

SDN Dev Group Week 3

• Preparation– Use UW-Madison OpenFlow testbed– Write an SDN application that relies on some

supporting modules from the controller (e.g., topology, spanning tree, etc.)

• Meeting topics– TBD