Network troubleshooting with Mirror VNets

Wundsam, Andreas; Mehmood, Amir; Feldmann, Anja; Maennel, Olaf

doi:10.1109/glocomw.2010.5700327

Cited by 9 publications

(6 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Accordingly, we devise a combined experiment on our testbed, confronting multimedia VOIP traffic with bursty, self-similar background traffic as found on the Internet, and routing both over a virtualized substrate based on XEN and OpenFlow with advanced debugging and flow management capabilities. Our results indicate that the advanced troubleshooting and management capabilities in the virtualized setup result in improved QoE, even though the level of isolation provided by the virtualization is limited [2].…”

Section: Case Studiesmentioning

confidence: 86%

Berlin: The Berlin Experimental Router Laboratory for Innovative Networking

Levin

Wundsam

Mehmood

et al. 2011

Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. Today's disruptive approaches to rearchitecting the Internet, e.g., Clean Slate Networking initiatives require testbeds that present unprecedented flexibility to the experimenter. This poster presents Berlin, a flexible testbed platform designed towards the requirements of Future Internet research. Berlin combines a diverse landscape of network elements, both software-defined and legacy hardware, and unifies them under a common management interface, presenting them as pluggable services to the experimenter.

show abstract

Section: Case Studiesmentioning

confidence: 86%

Berlin: The Berlin Experimental Router Laboratory for Innovative Networking

Levin

Wundsam

Mehmood

et al. 2011

Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…Record and replay techniques [20,35] instead allow users to step through (deterministic) executions and interactively examine the state of the system in exchange for runtime recording overhead. Within SDN, OFRewind [56] provides record and replay of OpenFlow channels between controllers and switches. Manually examining long system executions can be tedious, and our goal is to minimize such executions so that developers find it easier to identify the problematic code through replay or other means.…”

Section: Discussionmentioning

confidence: 99%

“…STS supports an interactive replay mode similar to OFRewind [56] that allows troubleshooters to query the state of the network throughout replay, filter subsets of the events, check additional invariants, and even induce new events that were not part of the original event trace. Similar to OFRewind, we do not run concurrent controller processes while the user is interactively performing replay, since proper replay across concurrent processes requires precise timing.…”

Section: Root Causing Toolsmentioning

confidence: 99%

Troubleshooting blackbox SDN control software with minimal causal sequences

Scott

Wundsam

Raghavan

et al. 2014

SIGCOMM Comput. Commun. Rev.

Self Cite

View full text Add to dashboard Cite

Software bugs are inevitable in software-defined networking control software, and troubleshooting is a tedious, time-consuming task. In this thesis we discuss how to improve control software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the software under test. We apply our technique to five open source SDN control platforms-Floodlight, NOX, POX, Pyretic, ONOS-and illustrate how the minimal causal sequences our system found aided the troubleshooting process. AcknowledgmentsMany thanks to the STS team for making this thesis possible:

show abstract

“…While we are not aware of works studying the allocation of reliable virtual networks, [29] considered the use of "shadow VNet", namely a parallel virtualized slice, to study the reliability of a network. However, such slice is not used as a back-up, but as a monitoring tool, and as a way to debug the network in the case of failure.…”

Section: Discussionmentioning

confidence: 99%

Designing and embedding reliable virtual infrastructures

Yeow

Westphal²,

Kozat³

2011

SIGCOMM Comput. Commun. Rev.

View full text Add to dashboard Cite

In a virtualized infrastructure where physical resources are shared, a single physical server failure will terminate several virtual servers and crippling the virtual infrastructures which contained those virtual servers. In the worst case, more failures may cascade from overloading the remaining servers. To guarantee some level of reliability, each virtual infrastructure, at instantiation, should be augmented with backup virtual nodes and links that have sufficient capacities. This ensures that, when physical failures occur, sufficient computing resources are available and the virtual network topology is preserved. However, in doing so, the utilization of the physical infrastructure may be greatly reduced. This can be circumvented if backup resources are pooled and shared across multiple virtual infrastructures, and intelligently embedded in the physical infrastructure. These techniques can reduce the physical footprint of virtual backups while guaranteeing reliability.

show abstract

Network troubleshooting with Mirror VNets

Cited by 9 publications

References 19 publications

Berlin: The Berlin Experimental Router Laboratory for Innovative Networking

Berlin: The Berlin Experimental Router Laboratory for Innovative Networking

Troubleshooting blackbox SDN control software with minimal causal sequences

Designing and embedding reliable virtual infrastructures

Contact Info

Product

Resources

About