| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | = OFCLEM Project Status Report = |
| | 4 | |
| | 5 | Period: 2Q10 |
| | 6 | == I. Major accomplishments == |
| | 7 | The project will deploy an !OpenFlow testbed on the Clemson University campus and connect with |
| | 8 | wireless mesh access points and mobile terminals. This trial will conduct !OpenFlow |
| | 9 | experimentation focused on !OpenFlow enabled network operation solutions as a precursor to |
| | 10 | deployment into Clemson research and production networks.[[BR]] |
| | 11 | |
| | 12 | During this period, key achievements include: |
| | 13 | a. Completed campus deployment of six !OpenFlow switches (4 HP + 2 Toroki) in three buildings. |
| | 14 | b. Completed functional test of !OpenFlow wireless mesh network setup; currently working on resolving observed !OpenFlow bottleneck, potentially due to flow table configuration issue. |
| | 15 | c. Completed development of a campus !OpenFlow management web portal featuring up-todate switch configuration status, performance monitoring, and automated user slices request/activation support. |
| | 16 | d. Campus facilities team has procured materials and scheduled fiber installation for small pilot network on one street (S. Palmetto Street in front of Fluor Daniel Building). |
| | 17 | e. Planned three Clemson campus demos and one cross-campus demo with Georgia Tech for GEC8. |
| | 18 | === A. Milestones achieved === |
| | 19 | Two milestones scheduled for this reporting period have not been completed pending inter-campus |
| | 20 | connectivity to be completed: |
| | 21 | 1. OFCLEM: S2.c Install GENI software with AM API implementation (Due 04/30/10 (late)) |
| | 22 | 1. OFCLEM: S2.d Begin integration testing with Stanford and BBN (Due 05/31/10 (late)) |
| | 23 | |
| | 24 | === B. Deliverables made === |
| | 25 | a. Completed campus !OpenFlow Ethernet deployment (opt-in users from two ECE labs) |
| | 26 | a. Completed campus !OpenFlow management portal |
| | 27 | a. Completed !OpenFlow-enabled wireless mesh network solution |
| | 28 | |
| | 29 | == II. Description of work performed during last quarter == |
| | 30 | |
| | 31 | === A. Activities and findings === |
| | 32 | a. Completed campus !OpenFlow Ethernet deployment[[BR]] Four HP !ProCurve 3500yl-48G switches and two Toroki LS4810 switches, all with OF 0.8.9 firmware, have been deployed in three ECE and CS buildings (topology can be seen at http://openflow.clemson.edu/trac/wiki/Network). Two more Toroki switches have been back-ordered. Three VLANs are configured on each switch and mapped consistently across the whole campus: non-!OpenFlow VLAN (130.127.39.128/25), !OpenFlow production VLAN (130.127.39.0/25), and !OpenFlow experimental VLAN (130.127.38.0/24). |
| | 33 | b. Completed campus !OpenFlow management portal[[BR]] The web portal is accessible to the public at http://openflow.clemson.edu to orient and assist new users to understand and request !OpenFlow slices for experimentation. With admin privilege one can also access the switch configuration database, real-time and historical performance charts, and internal development resources. |
| | 34 | c. Completed !OpenFlow-enabled wireless mesh network solution[[BR]] The wireless mesh network is based on PC Engines with dual radios (one IEEE 802.11b/g, one IEEE 802.11a/b/g). The b/g radio is !OpenFlow enabled and runs hostapd to accept client connections as an AP. The a/b/g (a mode used) radio runs OLSR mesh routing protocol to serve as the backbone. A layer 2 tunnel is created for each client to access the campus !OpenFlow experimental VLAN over the mesh network. The entire software configuration has been completed and end-to-end connectivity has been validated. Two remaining challenges are being investigated: 1) severe throughput loss due to potential !OpenFlow flow table configuration issue, 2) outdoor connectivity is still being investigated using multiple antenna models. |
| | 35 | |
| | 36 | === B. Project participants === |
| | 37 | The project team members are: |
| | 38 | PI: Kuang-Ching Wang, ECE Assistant Professor[[BR]] |
| | 39 | Co-PI: Jim Pepin, CTO[[BR]] |
| | 40 | IT: Dan Schmiedt, Director of Network Services and Telecommunications[[BR]] |
| | 41 | ECE graduate research assistants: Sajindra Pradhananga (MS), Glenn Evans (MS)[[BR]] |
| | 42 | ECE undergraduate students: Bradley Collins (senior), Aaron Rosen (senior), Bob |
| | 43 | Strecansky (senior), Patrick Baxter (junior), Ryan Izard (sophomore) |
| | 44 | |
| | 45 | === C. Publications (individual and organizational) === |
| | 46 | Not available at this time. |
| | 47 | |
| | 48 | === D. Outreach activities === |
| | 49 | None in this reporting period. |
| | 50 | |
| | 51 | === E. Collaborations === |
| | 52 | The project is conducted in collaboration with campuses and backbone providers on the !OpenFlow |
| | 53 | trial. We have so far worked more closely with: |
| | 54 | a. Nick !McKeown, Guru Parulkar, Guido Appenzeller and the Stanford !OpenFlow group, assisting us in the acquisition, installation, configuration, and testing of !OpenFlow software |
| | 55 | |
| | 56 | === F. Other Contributions === |
| | 57 | None in this reporting period. |
| | 58 | |
| | 59 | [[BR]] |
| | 60 | [[BR]] |
| | 61 | [[BR]] |
| | 62 | Converted submitted file by Julia Taylor (jtaylor@bbn.com). Original file can be found [http://groups.geni.net/geni/attachment/wiki/OFCLEM/1833A-OFCLEM-Report-10Q2.pdf here] |
