Aaron Gember Aditya Akella University of WisconsinMadison 1 Wisconsin Testbed Design Considerations Development Progress Highlevel design Problems encountered Lessons learned ID: 440167
Download Presentation The PPT/PDF document "SDN Dev Group, Week 2" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
SDN Dev Group, Week 2
Aaron Gember Aditya AkellaUniversity of Wisconsin-Madison
1
Wisconsin
Testbed
; Design ConsiderationsSlide2Development Progress
High-level design
Problems encounteredLessons learnedExperience with specific controllers2Slide3
Wisconsin
Testbed
3Slide4Testbed
ComponentsSwitches3x HP
ProCurve 54004x HP ProCurve 6600Servers15x 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)
4Slide5Testbed
Topology5
CS 4th Floor East4300E
ProCurve 6600
CS 4
th
Floor West
4300F
ProCurve
6600
CS 6
th
Floor West
6300E
ProCurve
5400
CS 6
th
Floor West
6300F
ProCurve
5400
CS 3360 (WINGS)WINGSProCurve 5400
CS 3390 (WAIL)WAILProCurve 6600
CS 3390 (WAIL)WAILTWOProCurve 6600
CS
Network
InternetSlide6Federation of network
testbeds: OpenFlow (campuses, NLR, I2), Emulab,
PlanetLab, etc.Live resource map: http://protogeni.net/flackGENI software stack: FlowVisor, FOAMExperimenters create a slice + slivers at each site to reserve the resources they want
6Slide7Testbed
for SDN Dev Group7
CS 3360 (WINGS)WINGSProCurve
5400
1
2
3
eth1.2**
eth1.2**
eth1.2**
thrush
lyrebird
vulture
wings-openflow-1
ControllerSlide8Accessing the
testbedSSH to wings-openflow-1.wail.wisc.edu(from anywhere on the Internet)
Username: CS username; Password: w3lcom3Reset your password by running passwdHome directory is shared using NFSLocal storage on each machine at /scratchSSH to vulture, thrush, and lyrebird to run commands on these end-hosts
8Slide9“Slices” for SDN Dev Group
Should reserve resources in FOAM/FlowVisor using GENI
RspecsStatically 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
9Slide10Design Considerations
Granularity of flow entriesStatic vs. dynamic flow installationSwitch flow table size limits
Policy inputCode re-use/modular design10Slide11SDN Dev Group Week 3
PreparationUse UW-Madison
OpenFlow testbedWrite an SDN application that relies on some supporting modules from the controller (e.g., topology, spanning tree, etc.) Meeting topicsTBD
11