Proceedings of the Second ACM SIGCOMM Workshop on Hot Topics in Software Defined Networking 2013
DOI: 10.1145/2491185.2491197
|View full text |Cite
|
Sign up to set email alerts
|

Leveraging SDN layering to systematically troubleshoot networks

Abstract: Today's networks are maintained by "masters of complexity": network admins who have accumulated the wisdom to troubleshoot complex problems, despite a limiting toolset. This position paper advocates a more structured troubleshooting approach that leverages architectural layering in SoftwareDefined Networks (SDNs). In all networks, high-level intent (policy) must correctly map to low-level forwarding behavior (hardware configuration). In SDNs, intent is explicitly expressed, forwarding semantics are explicitly … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
43
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 64 publications
(44 citation statements)
references
References 12 publications
1
43
0
Order By: Relevance
“…As previously observed [4], [3], network troubleshooting is generally still in a very early stage. "Rudimentary" probing tools like ping, traceroute, tcpdump, or nmap statistics are still being used for detecting network issues, but they are insufficient for large complex infrastructures with high amounts of traffic.…”
Section: Related Worksupporting
confidence: 59%
See 1 more Smart Citation
“…As previously observed [4], [3], network troubleshooting is generally still in a very early stage. "Rudimentary" probing tools like ping, traceroute, tcpdump, or nmap statistics are still being used for detecting network issues, but they are insufficient for large complex infrastructures with high amounts of traffic.…”
Section: Related Worksupporting
confidence: 59%
“…Second, debugging tools are typically linked to certain protocols. Many IT administrators of traditional networks are still using ping, traceroute and tcpdump, as noticed in [2], [3], but this is not scalable for large networks with multiple protocols (e.g., IPv4 and IPv6) that can even be encapsulated one into another. Third, network troubleshooting is hard because traffic can be forwarded over different/multiple paths in the network; forwarding devices and end-user devices are heterogeneous, or can be virtualised.…”
Section: Introductionmentioning
confidence: 99%
“…The purpose of the entire SDN paradigm is to translate high-level human intent to low-level network behavior via multiple logical and physical layers, and each layer performs part of this translation process [21]. The layering used in SDN is to present different levels of abstraction for the purpose of virtualization and central control.…”
Section: System Overviewmentioning
confidence: 99%
“…In MPI, we adopt the commonly used 5-layer SDN reference model as shown in Fig. 4, which is essentially the same as the one proposed in [21]. The task of translation between layers is conducted by various software components [5][6][7][8][9][10].…”
Section: System Overviewmentioning
confidence: 99%
“…In our understanding these issues also bear some relationship to Fault Tolerance. Heller et al [32] discuss the overall problem space regarding troubleshooting in SDN but the authors do not propose any system or framework. Scott et al [34] also deal with this aspect and in addition propose a troubleshooting system (called STS), which aims to alleviate the timeconsuming nature of debugging by eliminating events that are not causally related to the source of a failure.…”
Section: Fault Tolerance and Survivabilitymentioning
confidence: 99%