1 / 18

OFTEN Testing OpenFlow Networks

OFTEN Testing OpenFlow Networks. Maciej Kuźniar, Marco Canini*, Dejan Kostić EPFL *TU Berlin / T-Labs. Software-Defined Networking (SDN). Third-party program. When Faults Happen. Unreliable communication What is the rootcause?. Faults. NICE [NSDI’12]. Third-party program. OFTest

perrin
Download Presentation

OFTEN Testing OpenFlow Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OFTEN Testing OpenFlow Networks Maciej Kuźniar, Marco Canini*, Dejan Kostić EPFL *TU Berlin / T-Labs

  2. Software-Defined Networking (SDN) Third-partyprogram

  3. When Faults Happen • Unreliable communication • What is the rootcause?

  4. Faults NICE [NSDI’12] Third-partyprogram OFTest SOFT [CoNEXT’12] We need to test an integrated SDN network

  5. Testing Integrated Network OpenFlowprogram Host B Host A

  6. Testing Integrated Network Host A OpenFlowprogram Host B

  7. Challenges • Unmodified components • Switches as black boxes • Correctness definition • Avoid false positives

  8. NICE UnmodifiedOpenFlowprogram Environment model Host B Host A TopologyDescription Correctness Properties Switch1 Switch2

  9. State-Space Exploration State0 hostsend switchprocess_pkt State1 State3 State2 Define state and execute transitions ctrlpacket_in(pkt A) switchprocess_of ctrlpacket_in(pkt B) State9 State8 State6 State5 State4 State7

  10. OFTEN Test harness OpenFlowprogram Host B Host A Switch1 Switch2 Environment model HOW?

  11. Problem I: Transitions - Packes Test harness SwitchModel

  12. Problem I: Transitions – Control Messages Test harness SwitchModel

  13. Problem II: Synchronizing states Switch state • Flow table • Communication channels content

  14. Problem III: Defining Correctness • High-level correctness properties • Network-wide • User-defined • Switch-level Faulty controller Faulty switch or model

  15. Results • 3 applications • MAC-learning switch • Energy-aware traffic engineering • Web server load balancer • 3 switches • Reference Stanford implementation • Open vSwitch • HP ProCurve E5406zl

  16. Results Load-balancer issue • Send to the controller – 0 bytes Incorrect PacketIn message fields

  17. Conclusions OFTEN • Testing of an integrated network • Systematic state-space exploration • Real unmodified switches We need to test an integrated SDN network that contains all real components

  18. Future Work Integrated network testing • Required functionalities • Interface extensions

More Related