{"id":{"repo_id":"uiuc","oai_identifier":"oai:www.ideals.illinois.edu:2142/108342"},"canonical_url":"https://search.dev.ndltd.org/etd/uiuc/oai:www.ideals.illinois.edu:2142/108342","repository":{"repo_id":"uiuc","name":"University of Illinois - Urbana-Champaign","base_url":"https://www.ideals.illinois.edu/oai-pmh"},"display":{"title":"Transparent data plane failure tolerance for software defined networks","abstract":"With the ever-increasing size and scale of networks and the critical nature of user applications, it is very important to have adequate failure tolerance mechanisms in order to ensure minimal disruption is user operations. Rather than handling failures in the control plane, it is more desirable to have failure tolerance mechanisms in the data plane. To this end, Software Defined Networking (SDN) has introduced different measures for data plane failure tolerance in existing protocols. More specifically in OpenFlow, this is achieved through fast fail-over groups that monitor health of ports and route traffic along alternative ones when the primary port is unavailable. However, configuring fast fail-over groups in data plane has required all logic to be off loaded into controller applications. This not only makes these applications more complicated, but has also proven to be restrictive in terms of the application's architecture and programming constructs. In this thesis we introduce a novel design for SDN that abstracts out the failure tolerance logic from the control plane and automatically and transparently configures fast fail-over groups in the data plane, while leaving controller applications unmodified. Our technique pre-computes backup paths for each link in the data plane and installs them as MPLS tunnels. It then configures and installs fast fail-over groups to use these tunnels for rerouting traffic in the event of a link failure. Finally, it transparently intercepts communication between the control and data planes to use these fast fail-over groups and translate any other messages back and forth as needed. We also provide a module to make failure tolerance compatible with controller applications running in different versions of OpenFlow, particularly OpenFlow version 1.0, which has no notion of fast fail-over groups and integrates seamlessly with our design to make non-resilient controller applications failure tolerant. Our experiments demonstrate that our design is effective in transparently configuring fast fail-over groups for non-resilient controller applications, achieves a reasonably high throughput and incurs a fairly low performance overhead on network resources.","abstract_html":"With the ever-increasing size and scale of networks and the critical nature of user applications, it is very important to have adequate failure tolerance mechanisms in order to ensure minimal disruption is user operations. Rather than handling failures in the control plane, it is more desirable to have failure tolerance mechanisms in the data plane. To this end, Software Defined Networking (SDN) has introduced different measures for data plane failure tolerance in existing protocols. More specifically in OpenFlow, this is achieved through fast fail-over groups that monitor health of ports and route traffic along alternative ones when the primary port is unavailable. However, configuring fast fail-over groups in data plane has required all logic to be off loaded into controller applications. This not only makes these applications more complicated, but has also proven to be restrictive in terms of the application&#x27;s architecture and programming constructs. In this thesis we introduce a novel design for SDN that abstracts out the failure tolerance logic from the control plane and automatically and transparently configures fast fail-over groups in the data plane, while leaving controller applications unmodified. Our technique pre-computes backup paths for each link in the data plane and installs them as MPLS tunnels. It then configures and installs fast fail-over groups to use these tunnels for rerouting traffic in the event of a link failure. Finally, it transparently intercepts communication between the control and data planes to use these fast fail-over groups and translate any other messages back and forth as needed. We also provide a module to make failure tolerance compatible with controller applications running in different versions of OpenFlow, particularly OpenFlow version 1.0, which has no notion of fast fail-over groups and integrates seamlessly with our design to make non-resilient controller applications failure tolerant. Our experiments demonstrate that our design is effective in transparently configuring fast fail-over groups for non-resilient controller applications, achieves a reasonably high throughput and incurs a fairly low performance overhead on network resources.","abstract_has_math":false,"creators":["Farooq, Umar"],"institution":"University of Illinois at Urbana-Champaign","degree_name":"M.S.","degree_level":"Thesis","degree_discipline":"Computer Science","degree_department":null,"school":null,"contributors":["Caesar, Matthew"],"advisors":[],"committee_chairs":[],"committee_members":[],"year":2020,"date_issued":"2020-08-27T00:51:32Z","date_published":"2020-08-27T00:51:32Z","updated_at":"2026-07-22T22:24:48Z","subjects":["Software Defined Networking, Fast fail-over, failure tolerance, MPLS tunnels, data plane"],"languages":["en"],"rights":["Copyright 2020 Umar Farooq"],"rights_urls":[],"identifier_entries":[]},"links":{"outbound_url":"http://hdl.handle.net/2142/108342","outbound_label":"Handle","outbound_source":"dc:identifier"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor","label":"Contributor","values":["Caesar, Matthew"]},{"key":"dc:creator","label":"Author","values":["Farooq, Umar"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date","label":"Dc Date","values":["2020-08-27T00:51:32Z","2022-08-27T00:51:40Z","2020-05-12","2020-05"]},{"key":"dc:type","label":"Dc Type","values":["text","Thesis"]},{"key":"thesis:degree_discipline","label":"Discipline","values":["Computer Science"]},{"key":"thesis:degree_level","label":"Degree Level","values":["Thesis"]},{"key":"thesis:degree_name","label":"Degree Name","values":["M.S."]},{"key":"thesis:institution_name","label":"Thesis Institution Name","values":["University of Illinois at Urbana-Champaign"]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["Software Defined Networking, Fast fail-over, failure tolerance, MPLS tunnels, data plane"]}]},{"id":"language_rights","label":"Language and Rights","entries":[{"key":"dc:language","label":"Dc Language","values":["en"]},{"key":"dc:rights","label":"Dc Rights","values":["Copyright 2020 Umar Farooq"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["http://hdl.handle.net/2142/108342"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description","label":"Description","values":["With the ever-increasing size and scale of networks and the critical nature of user applications, it is very important to have adequate failure tolerance mechanisms in order to ensure minimal disruption is user operations. Rather than handling failures in the control plane, it is more desirable to have failure tolerance mechanisms in the data plane. To this end, Software Defined Networking (SDN) has introduced different measures for data plane failure tolerance in existing protocols. More specifically in OpenFlow, this is achieved through fast fail-over groups that monitor health of ports and route traffic along alternative ones when the primary port is unavailable. However, configuring fast fail-over groups in data plane has required all logic to be off loaded into controller applications. This not only makes these applications more complicated, but has also proven to be restrictive in terms of the application's architecture and programming constructs. In this thesis we introduce a novel design for SDN that abstracts out the failure tolerance logic from the control plane and automatically and transparently configures fast fail-over groups in the data plane, while leaving controller applications unmodified. Our technique pre-computes backup paths for each link in the data plane and installs them as MPLS tunnels. It then configures and installs fast fail-over groups to use these tunnels for rerouting traffic in the event of a link failure. Finally, it transparently intercepts communication between the control and data planes to use these fast fail-over groups and translate any other messages back and forth as needed. We also provide a module to make failure tolerance compatible with controller applications running in different versions of OpenFlow, particularly OpenFlow version 1.0, which has no notion of fast fail-over groups and integrates seamlessly with our design to make non-resilient controller applications failure tolerant. Our experiments demonstrate that our design is effective in transparently configuring fast fail-over groups for non-resilient controller applications, achieves a reasonably high throughput and incurs a fairly low performance overhead on network resources.","Submission published under a 24 month embargo labeled 'Closed Access', the embargo will last until 2022-05-01","The student, Umar Farooq, accepted the attached license on 2020-05-12 at 11:06.","The student, Umar Farooq, submitted this Thesis for approval on 2020-05-12 at 11:13.","This Thesis was approved for publication on 2020-05-12 at 21:25.","DSpace SAF Submission Ingestion Package generated from Vireo submission #15323 on 2020-08-25 at 17:44:18","Made available in DSpace on 2020-08-27T00:51:32Z (GMT). No. of bitstreams: 2 FAROOQ-THESIS-2020.pdf: 560567 bytes, checksum: d9b83e8de409ff56edfa2f1b00c3f6f3 (MD5) LICENSE.txt: 4208 bytes, checksum: 12e94bf82b706698b3b0751492b2193d (MD5) Previous issue date: 2020-05-12","Embargo set by: Seth Robbins for item 115957 Lift date: 2022-08-27T00:51:40Z Reason: Author requested closed access (OA after 2yrs) in Vireo ETD system","Author requested closed access (OA after 2yrs) in Vireo ETD system","Limited"]},{"key":"dc:format","label":"Dc Format","values":["application/pdf"]},{"key":"dc:title","label":"Title","values":["Transparent data plane failure tolerance for software defined networks"]}]}],"canonical_facts":{"dc:contributor":["Caesar, Matthew"],"dc:creator":["Farooq, Umar"],"dc:date":["2020-08-27T00:51:32Z","2022-08-27T00:51:40Z","2020-05-12","2020-05"],"dc:description":["With the ever-increasing size and scale of networks and the critical nature of user applications, it is very important to have adequate failure tolerance mechanisms in order to ensure minimal disruption is user operations. Rather than handling failures in the control plane, it is more desirable to have failure tolerance mechanisms in the data plane. To this end, Software Defined Networking (SDN) has introduced different measures for data plane failure tolerance in existing protocols. More specifically in OpenFlow, this is achieved through fast fail-over groups that monitor health of ports and route traffic along alternative ones when the primary port is unavailable. However, configuring fast fail-over groups in data plane has required all logic to be off loaded into controller applications. This not only makes these applications more complicated, but has also proven to be restrictive in terms of the application's architecture and programming constructs. In this thesis we introduce a novel design for SDN that abstracts out the failure tolerance logic from the control plane and automatically and transparently configures fast fail-over groups in the data plane, while leaving controller applications unmodified. Our technique pre-computes backup paths for each link in the data plane and installs them as MPLS tunnels. It then configures and installs fast fail-over groups to use these tunnels for rerouting traffic in the event of a link failure. Finally, it transparently intercepts communication between the control and data planes to use these fast fail-over groups and translate any other messages back and forth as needed. We also provide a module to make failure tolerance compatible with controller applications running in different versions of OpenFlow, particularly OpenFlow version 1.0, which has no notion of fast fail-over groups and integrates seamlessly with our design to make non-resilient controller applications failure tolerant. Our experiments demonstrate that our design is effective in transparently configuring fast fail-over groups for non-resilient controller applications, achieves a reasonably high throughput and incurs a fairly low performance overhead on network resources.","Submission published under a 24 month embargo labeled 'Closed Access', the embargo will last until 2022-05-01","The student, Umar Farooq, accepted the attached license on 2020-05-12 at 11:06.","The student, Umar Farooq, submitted this Thesis for approval on 2020-05-12 at 11:13.","This Thesis was approved for publication on 2020-05-12 at 21:25.","DSpace SAF Submission Ingestion Package generated from Vireo submission #15323 on 2020-08-25 at 17:44:18","Made available in DSpace on 2020-08-27T00:51:32Z (GMT). No. of bitstreams: 2 FAROOQ-THESIS-2020.pdf: 560567 bytes, checksum: d9b83e8de409ff56edfa2f1b00c3f6f3 (MD5) LICENSE.txt: 4208 bytes, checksum: 12e94bf82b706698b3b0751492b2193d (MD5) Previous issue date: 2020-05-12","Embargo set by: Seth Robbins for item 115957 Lift date: 2022-08-27T00:51:40Z Reason: Author requested closed access (OA after 2yrs) in Vireo ETD system","Author requested closed access (OA after 2yrs) in Vireo ETD system","Limited"],"dc:format":["application/pdf"],"dc:identifier":["http://hdl.handle.net/2142/108342"],"dc:language":["en"],"dc:rights":["Copyright 2020 Umar Farooq"],"dc:subject":["Software Defined Networking, Fast fail-over, failure tolerance, MPLS tunnels, data plane"],"dc:title":["Transparent data plane failure tolerance for software defined networks"],"dc:type":["text","Thesis"],"thesis:degree_discipline":["Computer Science"],"thesis:degree_level":["Thesis"],"thesis:degree_name":["M.S."],"thesis:institution_name":["University of Illinois at Urbana-Champaign"]},"updated_at":"2026-07-22T22:24:48Z"}