Proceedings of the 14th ACM Workshop on Hot Topics in Networks 2015
DOI: 10.1145/2834050.2834099
|View full text |Cite
|
Sign up to set email alerts
|

Destroying networks for fun (and profit)

Abstract: Network failures are inevitable. Interfaces go down, devices crash and resources become exhausted. It is the responsibility of the control software to provide reliable services on top of unreliable components and throughout unpredictable events. Guaranteeing the correctness of the controller under all types of failures is therefore essential for network operations. Yet, this is also an almost impossible task due to the complexity of the control software, the underlying network, and the lack of precision in sim… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
3
0

Year Published

2016
2016
2024
2024

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 14 publications
(3 citation statements)
references
References 25 publications
0
3
0
Order By: Relevance
“…Encouraged by the success of testing techniques in distributed systems, Shelly et al [167] designed and implemented Armageddon [168], which introduces systematic chaos into SDN networks. Armageddon introduces failures (e.g., some ports being down) without violating network invariants.…”
Section: Techniques For Networkmentioning
confidence: 99%
“…Encouraged by the success of testing techniques in distributed systems, Shelly et al [167] designed and implemented Armageddon [168], which introduces systematic chaos into SDN networks. Armageddon introduces failures (e.g., some ports being down) without violating network invariants.…”
Section: Techniques For Networkmentioning
confidence: 99%
“…Network administrators must know whether the network is correct [24], e.g., whether destination t is reachable from source s, or whether the forwarding rules present in the network imply that packets may potentially be sent in a cycle. Often such network properties are checked by constantly sending probe packets into the network, or, alternatively, by sending the state of all nodes in the network to a central location where all the data is then verified.…”
Section: Introductionmentioning
confidence: 99%
“…Although most DCN topologies are symmetrical, in practice, DCNs turn out to be often asymmetrical because of frequent failures of network elements (e.g., switches, links, and ports); for example, up to 40 link failures per day [15,16]. However, the performance of some load-balancing schemes depending on symmetrical characteristic of topology deteriorates significantly under asymmetrical topologies (e.g., equal-cost multi-path (ECMP) [3] and Presto [8]).…”
mentioning
confidence: 99%